Maël Nison

Can you look to add a test? You can use the `unconventional-tarball` package from within the tests to get a package that generates an `__archiveUrl` locator.

I'm not certain about this fix without a regression test, as I don't quite understand the issue - from what I see we're iterating over all resolutions and saving them...

Indeed, the `yarn version` implementation is a little weird. I'm a little wary of touching it outside of a major release, but rewriting it is definitely in my plans.

> yarn delegate many functions to NPM No.

Yarn can't do much, it's your kernel that kills the process with no opportunity to react (if it was Node, you'd have a page fault error with memory addresses etc).

Yarn catches error codes from its subprocesses (and it's quite uncommon to have subprocesses during the fetch step), so that's very unlikely to be the case. I don't know exactly...

The unzip process is performed in wasm-land (for portability), so the memory grows but never shrinks. I experimented in https://github.com/yarnpkg/berry/pull/5738 to move this part in JS-land (initially for performances, but...

I've been toying with the idea of using v86 in the [yarnpkg.com](https://yarnpkg.com) website to support its tutorials and perhaps make it easier for users to share bug reproductions. Being able...

That sounds a worthwhile experiment. I think it was quickly discussed a couple of years ago and at the time my thinking was that this could lead to easy cache...

(I misread hardlinks & reflinks - of note, "Requires NAPI or other native helper which can do syscalls", this isn't something possible today, as Yarn currently must be distributed as...