You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding things here exposes them to allow packages in your monorepo, instead of having to modify a pnpmfile.js entry for each package, or use overrides.
LATER: Can probably make this a nice table, or publish on the website (use remark-github to linkify issues from Docusaurus).
Legend
cli-pr = a pr to allow bootstrapping the framework with pnpm (in addition to yarn and npm)
guide = an issue on pnpm repo to track getting the package to work and other PRs open to fix issues with other tools
Tracking popular framework's and their pnpm support.
There are two main issues:
e.g. create-react-app --pnpm
a. Bootstrapping
We can track PRs on the framework repos in this issue.
b. Functionality
Here are common approaches for fixing broken packages:
.npmrc
>public-hoist-pattern[]=x
package.json > overrides
@vjpr/metro-0.59.vjpr.1
)pnpmfile.js
--shamefully-flatten
The most common issues are:
node_modules/.pnpm
store)public-hoist-pattern
There are some defaults built-in.
['*types*', '*eslint*', '@prettier/plugin-*', '*prettier-plugin-*']
Adding things here exposes them to allow packages in your monorepo, instead of having to modify a
pnpmfile.js
entry for each package, or useoverrides
.pnpm.overrides
Useful for patching packages or enforcing a single version to be resolved (good for fixing singletons).
pnpmfile
Publishing packages that you can import to fix packages
@pnpmfile npm org
pnpmfile declarative format
Berry (Yarn 2) is tracking their required
overrides
here.Latest idea was
overrides.json
instead of pnpmfile.The text was updated successfully, but these errors were encountered: