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
During a docker deployment, I use pnpm --prod --no-optional deploy which excludes all dev and optional dependencies. However, there is a specific set of dependencies that I do want to include with the deployment. Whats the best way to do this?
I thought that specifying a packageExtension where I override the 'optional' to make it 'regular' would work. However, this does not seem to be honored. If I run pnpm --prod deploy without the --no-optional then it works, but it pulls in a lot of unnecessary optional dependencies.
i.e.
package A (1.0.0) has an optional dependency B (1.0.0)
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
Uh oh!
There was an error while loading. Please reload this page.
-
During a docker deployment, I use
pnpm --prod --no-optional deploy
which excludes all dev and optional dependencies. However, there is a specific set of dependencies that I do want to include with the deployment. Whats the best way to do this?I thought that specifying a packageExtension where I override the 'optional' to make it 'regular' would work. However, this does not seem to be honored. If I run
pnpm --prod deploy
without the--no-optional
then it works, but it pulls in a lot of unnecessary optional dependencies.i.e.
package A (1.0.0) has an optional dependency B (1.0.0)
Beta Was this translation helpful? Give feedback.
All reactions