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
I am using PnP and would like that only the declared dependencies (not devDependencies) in the package.json are available to the application when node is running in production mode (NODE_ENV=production).
So I would expect Yarn's PnP resolver to throw an error when requesting a package that is required when running the application in production mode, but is declared in the devDependencies of package.json.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am using PnP and would like that only the declared dependencies (not devDependencies) in the package.json are available to the application when node is running in production mode (NODE_ENV=production).
So I would expect Yarn's PnP resolver to throw an error when requesting a package that is required when running the application in production mode, but is declared in the devDependencies of package.json.
Is there an option to achieve that?
Beta Was this translation helpful? Give feedback.
All reactions