Maël Nison

Yep for sure, JS isn't ready for the kind of protected environment we need, and I'm really glad to see both TC39 and Node tackling this issue! 🌟 My point...

In case you find it useful, we solved this problem in Yarn by specifying that "standard registry patterns" are of the form: ``` ///-/-.tgz ``` If the tarball in metadata...

Indeed, but we didn't get requests to make it work nonetheless. Notably, a few issues have been raised by people using them, as evidenced by the logs they shared, but...

This is something that we (Yarn) are interested in supporting as well. My comments: - One question I have is regarding the expected efficiency. Finding the right set of packages...

I remember - the suggestion to use peer dependencies to define singletons looked interesting (but unfortunately relies on the ecosystem doing the right thing, which is a assumption that's been...

> D3 is bulky and might want to be a singleton by default. However, some pages might not care about bulkiness or are not using the full library, so the...

> All it takes is for 1 thing to list `"react": "^0.15"` as a dependency for a dupe to silently be introduced. Consider that `npm install --save react` will do...

Right, hence why those settings are suggestions, but not requirements. Those who won't use those packages the ninety-nine-percentil-way exist (as I said in my post I'm even one of them!),...

While a little off-topic, I'm open to add support for a `libc` field in Yarn. Main issue I'd have is the difficulty around detecting it (`detect-libc` is a good start,...

Right, the implementation of the skip mechanism will be up to each package manager, I'm not too worried about that. My point is that knowing whether the system uses the...