-
Notifications
You must be signed in to change notification settings - Fork 948
New issue
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
feat(vue-next): minify webpack bundle size #3983
Conversation
Current ttypescript version not support node v16.20.2, the latest v16 version. It will cause this issue: cevek/ttypescript#150
align patchProps types with vue runtime core, but there also have some spec tests to fix
just like fromSsrAstNodes, optimize the output in hippy-vue-css-loader, and make hippy-vue-next-style-parser to compatible with old and new format.
webpack.NamedModulesPlugin was deprecated in v4 and removed in v5. these plugin are default in devlopment mode and should not be configured in production mode, because it will expose file path and increase bundle sizes. https://v4.webpack.js.org/migrate/4/#deprecatedremoved-plugins
|
Hi, @yokots. Thanks for your PR! 👏 🏷️ You can leave a comment in this PR with |
After a quick scan, I have approved workflow to run.
🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators. |
* chore(drive/js): bump up ttypescript version Current ttypescript version not support node v16.20.2, the latest v16 version. It will cause this issue: cevek/ttypescript#150 * fix(hipp-vue-next): correct patchProps types align patchProps types with vue runtime core, but there also have some spec tests to fix * refactor(vue-next): minify generated style code just like fromSsrAstNodes, optimize the output in hippy-vue-css-loader, and make hippy-vue-next-style-parser to compatible with old and new format. * build(example-scripts): remove webpack.NamedModulesPlugin webpack.NamedModulesPlugin was deprecated in v4 and removed in v5. these plugin are default in devlopment mode and should not be configured in production mode, because it will expose file path and increase bundle sizes. https://v4.webpack.js.org/migrate/4/#deprecatedremoved-plugins * chore(examples): update vue3 assets --------- Co-authored-by: zealotchen <92966734+zealotchen0@users.noreply.github.com>
just see each commit message.
Before submitting a new pull request, please make sure: