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
It's extremely annoying that devDeps are bundled with buildDeps into the same category. If I want to create a workflow that purely builds my frontend projects, why must I install Jest and Puppeteer which I use for testing my project?
This is extremely visible in unified server/client codebases as all the client dependencies could be thought of as buildDependencies instead of pure dependencies that won't get pruned with NODE_ENV=production prune and will just fill valuable server disk space that they don't actually need
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
-
It's extremely annoying that devDeps are bundled with buildDeps into the same category. If I want to create a workflow that purely builds my frontend projects, why must I install Jest and Puppeteer which I use for testing my project?
This is extremely visible in unified server/client codebases as all the client dependencies could be thought of as
buildDependencies
instead of pure dependencies that won't get pruned withNODE_ENV=production prune
and will just fill valuable server disk space that they don't actually needBeta Was this translation helpful? Give feedback.
All reactions