It's been a tough last week — my whole family has COVID, so I'm running on low energy mode. Still, I've managed to put together this issue, which includes a really useful Nuxt tip on naming file chunks. This can help you analyze large chunks in your production bundles. Hope you find it helpful!
👉🏻 When using `nuxi init` to scaffold a new Nuxt application and choose NPM as package manager, you might've seen deprecation warnings.
👉🏻 Alex explains if they are relevant and what they do say.
💡 Nuxt Tip: Add Filenames to Your Nuxt Chunks
In one of my customer's projects, we had a problem with one Nuxt client chunk that was too large (>1MB).
We used the nuxt analyze CLI command to analyze the production bundle and identify which chunk was too large.
The command generates a URL that you can open in your browser to see a visual representation of your bundle:
Unfortunatly, the chunk names are not very descriptive because they are hashed. To make them more descriptive, you can add the following code to your nuxt.config.tsnuxt.config.ts file:
👉🏻 Focus on unit tests with the right scope, avoid unnecessary component tests, and leverage stable APIs to create scalable integration tests that require minimal maintenance.
👉🏻 Having good tests helps maximize engineering velocity, and automated generated tests may help codebases be better tested in the future.