fix: clean yarn lock

[oliveriosousa]

• Cleans all the content of yarn.lock

Aims to test the real resolution of yarn with a clean install every time we run yarn install

NOTE: We cannot delete this file because it is being used to force aegir to use yarn as package manager.

[oliveriosousa]

Apparently, we have errors when used as a mono repo 🤔

../../node_modules/ipfs-unixfs-importer/esm/src/chunker/rabin.js:83:41-47 - Error: export 'create' (imported as 'create') was not found in 'rabin-wasm' (possible exports: __esModule, importer)

../../node_modules/ipfs-unixfs-importer/esm/src/dag-builder/dir.js:8:23-29 - Error: export 'UnixFS' (imported as 'UnixFS') was not found in 'ipfs-unixfs' (possible exports: __esModule, importer)

https://github.com/ipfs-examples/js-ipfs-examples/pull/42/checks?check_run_id=3622625347

Any suggestion?

May fix this issues too... #36 #35

@hugomrdias @achingbrain

[achingbrain]

This seems to be related to how yarn installs deps - it's breaking something in webpack.

Further discussion with a simple repro case: webpack/webpack#14268

[oliveriosousa]

Apparently continues to fail when running the example browser-next as a monorepo.

../../node_modules/ipfs-unixfs-importer/esm/src/chunker/rabin.js
Attempted import error: 'create' is not exported from 'rabin-wasm' (imported as 'create').

My guess is some yarn resolution is being resolved incorrectly, it resolves webpack v5.53 with "enhanced-resolve": "^5.8.0" as dependency but then we have enhanced-resolved v4.5.0 installed.

Locally, custom-ipld-formats runs fine as standalone but in the CI fails with: HTTPError: Invalid request query input

[achingbrain]

Superseded by #43