Maël Nison

Until now, loaders didn't affect the resolution / load steps of subsequent loaders. For example, it wasn't possible to have loaders written in TypeScript, because the TypeScript loader wouldn't be...

As far as I can tell my [questions](https://github.com/nodejs/node/pull/44732#issuecomment-1253914637) are still relevant, and I'd need some guidance on what's the appropriate strategy here.

Yes, we just released 3.3.0 which should solve this problem.

We have a thing called [documentation](https://yarnpkg.com/configuration/yarnrc#telemetryUserId): > By default, we don't assign unique IDs in the telemetry we send, so we have no way to know which data originates from...

I optimized `yarn run` a bit by stripping useless module evaluations; it's a tiny bit better, but not amazing either: https://github.com/yarnpkg/berry/pull/6188 If someone wants to help improve that further!

It'll not be backported to 3.x considering it's a breaking change, and very difficult to cherry pick anyway. If you need it, please use the RCs.

> Why would we want it enabled by default in docker if it's not enabled by default in node itself? Shouldn't those two happen at the same time, or not...

It's worth double-checking when the time comes to enable it by default on all distributions, but I believe so; opt-in was suggested to derisk the project (https://github.com/nodejs/node/pull/35398#issuecomment-700780197, https://github.com/nodejs/node/pull/35398#issuecomment-700791438), but the...

I already implemented the PnP resolution for Rust as a crate, in https://github.com/arcanis/pnp-rust. I'm very open to merge any change necessary to make it easier to use on your side.

Up. Contrib clean is currently not able to delete symlinks. Maybe adding an option would be enough without breaking BC ?