feat: public-hoist-pattern

[zkochan]

close #2628

[aparajita]

One question: can the hoist pattern be specified by a setting in a per-package .npmrc?

[zkochan]

No, currently hoisting is not possible per package. It can be set once for a monorepo or once for a project with a single package.json

[aparajita]

Once for a monorepo or once for a project with a single package.json is sufficient. So the user would set public-host-pattern=<pattern> in the project .npmrc?

[zkochan]

Yes. But I think we will be updating the default value of that setting when we will find issues in the ecosystem. This way new users will not get disappointed by pnpm. I think @vjpr might have a list already

[aparajita]

Sounds good, just want to be sure all this is well documented.

[zkochan]

sorry for all the notifications. Hopefully, now it will pass.

[vjpr]

we will be updating the default value of that setting when we will find issues in the ecosystem.

This is a really interesting solution.

But usually the fixes for such packages are to add the missing dependency or peerDependency using the pnpmfile to the individual packages. Its just that the pnpmfile is a little too tricky to use.

[zkochan]

I think there are some buggy pluggable frameworks like angular and karma that might benefit from this feature.

Like angular now only works with shamefully-flatten. Maybe we can come up with a pattern that is not * to fix the angular issues. Or maybe not. I don't know yet.

[vjpr]

Is there a GH issue open for Angular support?

[aparajita]

See my proposal in #2634 for an elegant way to deal with individual packages that would be too difficult for a pattern to deal with.

[aparajita]

Maybe we can come up with a pattern that is not * to fix the angular issues. Or maybe not. I don't know yet.

@zkochan See my proposal in #2634