Maël Nison

I just deployed the documentation to the website: https://yarnpkg.com/advanced/pnp-spec/

I've opened https://github.com/yarnpkg/berry/pull/4724 to address the problems you pointed. A few notes: > I have updated my branch here, including incorporating the tests: https://github.com/evanw/esbuild/tree/yarn-pnp I tried it and it worked...

Regarding the workspaces not resolving thing, I dig a bit, and it seems to be caused by Esbuild not detecting the PnP file. Adding a log [here](https://github.com/evanw/esbuild/commit/50b47d779d7f33c9fb5c998ac5557f284458425e#diff-ff3593e6a6cb00f927118c829760e054ccca7686eae492f9f4f18b9b851a9a20R696), I get the...

Scratch my previous post - the reason is just that we changed the hook format in https://github.com/yarnpkg/berry/pull/4320; before: ```js #!/usr/bin/env node /* eslint-disable */ try { Object.freeze({}).detectStrictMode = true; }...

From the last loaders [meeting notes](https://github.com/nodejs/loaders/blob/e70e6c859d65904e968c0eafe7857d44a766f3b5/doc/meetings/2022-11-08.md): > @arcanis will rebase https://github.com/nodejs/node/pull/43772, we’ll re-review it, and assuming it’s fine we’ll land it, and it can be released in 19.x. I’ll mark...

I'm not aware of any bug in the PnP implementation. Last time I checked this thread the problem seemed to be related to how Webpack crawl the filesystem for changes,...

> We already do it, but we can't get list of files, so we can't track them You don't need to track them - the zip archives can be assumed...

I should add a note about it to our documentation, for sure. > Adding a new top-level binary is likely to be a nonstarter; `npx` is already regretted. This isn't...

Make install scripts able to cross-refer to other scripts without having to hardcode package manager names (or use `$npm_execpath`, which practically noone does).

Although it doesn't solve the underlying portability problem, it actually works for Yarn Modern even on Windows.