plugins
field will be passed to import() expression
. Users can resolve the plugin module path by themselves (like require.resolve('prettier-plugin-foo')
). See the doc.Strings provided to plugins are ultimately passed to import() expression, so you can provide a module/package name, a path, or anything else import() takes.
Therefore, now is the proper time for removing the default option *eslint*
and *prettier*
from public-hoist-pattern
. Users will get a clean and consistent node_modules
folder. Hiding *eslint*
and *prettier*
in public-hoist-pattern
seems not a wise choice.
Remove the default option *eslint*
and *prettier*
from public-hoist-pattern
option.
https://pnpm.io/npmrc#public-hoist-pattern
Describe the drawbacks of your solutionThis is a breaking change.
Describe alternatives you've consideredNo.
waynebrantley, twhitex, CharlieWallace17, gluxon, PabloSzx and 9 morekarlhorky and aehardingkarlhorky
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4