My Quasar CLI project with Vite build process takes a long time (hours) #16953
-
After that it doesn't do anything else and in the dist/spa folder only the icons are created |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
|
Hi, I don't think anyone will be able to help you or at least guide you to find the culprit. Please provide a reproduction repo with clear instructions on how to reproduce. |
Beta Was this translation helpful? Give feedback.
-
|
The build was already done, but it was after a long time (hours), is it normal for it to take so long in large projects? |
Beta Was this translation helpful? Give feedback.
-
|
Definitely not. There‘s something in your specific case that has a bug. Could be a Vue plugin, a Vite plugin, something in your code or even the machine that you are building on. Would gladly help you, but I need your project to investigate with, otherwise we‘re just playing the guessing game. If you‘d like, you can contact me on Discord directly to find a way. |
Beta Was this translation helpful? Give feedback.
-
|
and there is no way for me to see the details of what is happening during the build process so I can detect what is causing the error? |
Beta Was this translation helpful? Give feedback.
-
Hey sorry to burry out this post, but I actually have the same issue, my build are taking ages. Not 3hrs, but a significant time since I added capacitor. Each time I'm building in spa mode to be sure it doesn't buld for the other platform but it takes really way longer than before. I'll provide you an acces to a private repo if you're up to help ^^ Thanks |
Beta Was this translation helpful? Give feedback.
-
|
@mr-Sepi0l please see #16953 (comment) to hopefully debug your problem |
Beta Was this translation helpful? Give feedback.
-
I wrote to you on discord |
Beta Was this translation helpful? Give feedback.
-
|
Please, I still have the problem, the build process always takes 3 hours, help please 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Can someone help me with an option to debug the build process? I need to detect what is causing the build to take more than 3 hours. quasar dev --debug: don' t show anything HELP PLEASE!!! 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
You can try |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much, @yusufkandemir , your answer guided me in the right direction. $env:DEBUG="quasar:*"; quasar build --debugThis gave me the possibility to see that the problem was being caused by the web-fonts of my project, specifically nucleo-icons and another custom one created with nucleo-icons; although when I removed them from the project, it also stopped for hours with line-awesome or the material design ones, so it was any icon library and the message in the logs was the following: Solution: chunkSizeWarningLimit: 1000, // Increase the limit to 1 MBAlthough I also added the following plugins in quasar.config.js: build: {
// ... others configurations
vueRouterMode: 'hash',
extendViteConf(viteConf) {
viteConf.build.rollupOptions = {
output: {
manualChunks(id) {
if (id.includes('node_modules')) {
return 'vendor'; // Separa las dependencias externas en un chunk separado
}
}
}
};
},
chunkSizeWarningLimit: 500,
// ... others configurations
vitePlugins: [
{
name: 'ignore-fonts',
enforce: 'post',
resolveId(id) {
if (/\.(woff|woff2|ttf|eot|svg)$/.test(id)) return id;
return null;
},
load(id) {
if (/\.(woff|woff2|ttf|eot|svg)$/.test(id)) return '';
return null;
}
}
]
} |
Beta Was this translation helpful? Give feedback.
Thank you very much, @yusufkandemir , your answer guided me in the right direction.
In my case, I use Windows, in Powershell you can use the following command:
This gave me the possibility to see that the problem was being caused by the web-fonts of my project, specifically nucleo-icons and another custom one created with nucleo-icons; although when I removed them from the project, it also stopped for hours with line-awesome or the material design ones, so it was any icon library and the message in the logs was the following: