We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendor.js
I updated Ember from 5.5.0 to 5.6.0 and my build failed because vendor.js in a production (minified) build grew by 52 KB.
ember new ember-test --pnpm cd ember-test ember serve --environment=production
Copy the dist/assets/vendor-*.js somewhere. Downgrade ember-source to 5.5.0. Run a prod build again. Compare the two vendor-XXX.js files.
dist/assets/vendor-*.js
ember-source
vendor-XXX.js
vendor.js is 52 KB more.
No such huge difference.
A bit of discussion: https://discord.com/channels/480462759797063690/1199763691101503488
cc @wycats, @NullVoxPopuli
The text was updated successfully, but these errors were encountered:
Perhaps @ef4 might have an idea?
Sorry, something went wrong.
I mean, the biggest thing that changed were some glimmer-vm upgrades, so it's possible that that caused the bloat.
It would be great to see some bundle analysis
Upgrade the Glimmer VM from 0.84.3 to 0.85.13
v5.6.0
5.7.0 is 5kb less than 5.6.0. But still lots more than 5.5.0. 😢
No branches or pull requests
🐞 Describe the Bug
I updated Ember from 5.5.0 to 5.6.0 and my build failed because
vendor.js
in a production (minified) build grew by 52 KB.🔬 Minimal Reproduction
ember new ember-test --pnpm cd ember-test ember serve --environment=production
Copy the
dist/assets/vendor-*.js
somewhere. Downgradeember-source
to 5.5.0. Run a prod build again. Compare the twovendor-XXX.js
files.😕 Actual Behavior
vendor.js
is 52 KB more.🤔 Expected Behavior
No such huge difference.
🌍 Environment
A bit of discussion:
https://discord.com/channels/480462759797063690/1199763691101503488
cc @wycats, @NullVoxPopuli
The text was updated successfully, but these errors were encountered: