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
When running meteor build --server-only on a clean project (just freshly created by the command meteor create test-project) I end up with a folder of a size of 118mb - of which 74mb is taken up by programs/server/npm/node_modules/meteor/babel-compiler. I'm quite unsure if the rest wouldn't be needed, but if we could get out the babel-compiler here, that would decrease the size of our final bundle considerably.
Packages like TypeScript, PostCSS and etc. can be safely remove because it is "build step" tools.
Remove duplications from build
There are multiple versions of the same package in different places. That's how Meteor packages system work. But maybe we can build one package graph for all deps and use it in meteor packages.
The benefits
Smaller image(archive) size => decreasing bandwidth usage when deploying app.
Faster build time (we can install all deps tree at once without duplications in sub folders). ???
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
-
From issue: #10902
In the issue @SimonSimCity mentioned:
@ensemblebd had a workaround
Another interesting issue #10230
What we can do
Remove dev dependencies from build
Packages like TypeScript, PostCSS and etc. can be safely remove because it is "build step" tools.
Remove duplications from build
There are multiple versions of the same package in different places. That's how Meteor packages system work. But maybe we can build one package graph for all deps and use it in meteor packages.
The benefits
Beta Was this translation helpful? Give feedback.
All reactions