Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Nuxt Performances: Present and Future #6467
On top of letting your write Vue files, creating pages with the filesystem and managing your SEO with vue-meta, the NuxtJS team and contributors worked a lot of shipping by default an efficient and performant web application.
What do we have today:
What do we plan to do:
How to accomplish this:
Maintaining an open source project requires consistent effort, not just with adding code, but also code reviews and support. The NuxtJS team and contributors coordinates their efforts on Discord. We all work on our free time to maintain it and I do believe the Chrome Performance Fund could help us to pay ourselves and our contributors on this future work thanks to our Open Collective.
I'm happy to share Chrome is donating $12,000 to support Web Performance optimizations on the Nuxt.js roadmap
In particular, we're excited to see the project explore the proposed work on:
We know the work to upgrade to Webpack 5 has been a long one and are looking forward to seeing those changes land too! We hope this funding helps support your work just a little :)
Can you consider reducing the size of nuxt in the production environment?
I found that when using Docker to package images, even in a production environment, the size is 400 ~ 500M, which is a waste of resources
So users can run the application by running the following command
> nuxt build > cd ./dist > ls -lh total 44040192 -rw-r--r-- 1 root staff 44040192B 12 29 13:45 index.js > node ./index.js Listen on port 3000
I hope the final production environment file is ideal in the size of
@axetroy I've spent some time slimming Nuxt Docker images, and
If you are starting Nuxt programmatically, you could try listing just
The issue you highlight is, I think, not an issue with Nuxt per se but in the nature of node_modules-based projects.