Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi, i am testing the new integration with vite, everything works fine, but when i run npm run build vite generates one javascirpt file per component, what i need to change to make vite generate a vendor file and another file for all the other components?
If anyone was having the same problem the solution was to change this line in app.js:
resolve: (name) => resolvePageComponent(`./Pages/${name}.vue`, import.meta.glob('./Pages/**/*.vue')),
to
resolve: (name) => resolvePageComponent(`./Pages/${name}.vue`, import.meta.globEager('./Pages/**/*.vue')),
@Damage Inc Not sure why you want to disable code splitting :) If its just because you want to compile all vendor files into one file, you can use manualChunks`: let me know if you want help implementing that instead.
Anyways. I just tested it, and my IDE complains that globEager() is deprecated.
The official docs says to use
resolve: (name) => resolvePageComponent(./Pages/${name}.vue, import.meta.glob('./Pages/**/*.vue', {eager: true})),
@Sinnbeck is just because i don't want like 10-15 requests to the server (even if they are small files) every time the user changes from one part of the system to another
@Damage Inc Ok cool. But I still suggest you use the syntax from the docs, just in case the globEager function is removed.
@Sinnbeck Ok, thanks for the advise.
@Damage Inc Anytime. Remember to mark a best answer to close the thread.
And can I suggest you read this? https://blog.jakoblind.no/how-code-splitting-increases-performance/ Often code splitting is faster, as clients does not need to download the full js file if you make a new release. They only need to download the tiny split out file that contains the changes. :)
Please or to participate in this conversation.