I have already updated the project as well, for the latest version of Quasar. Is that I was afraid to upgrade, because when I updated from 0.14. * To 0.15.2, my project was totally different, had to program again a 4 pages I had already done. I think that happened because it changed a lot from one version to another.
Well, I’m loving programming with Quasar, an exceptionally wonderful framework.
Inspecting this in more depth, and being a bit more open-minded I can understand that this is maybe a feature.
Looking at the bundles on more detail I can see that they are not of the same exact size, and if you look closer you can see that they do not include the same files. Being each bundle a different route maybe this makes sense. Each route has just the files they need. Because we don’t know how routes will be loaded (which order)because can navigate to any random one we have to include all the possible files they may require.
My only complain may be that some files are present both at the vendor bundle and the route bundle. Since the vendor bundle is loaded on every route, I don’t see why those files needs to be included on the route bundle too.
In any case, this is just an unnecessary optimization concern, since page loading is already very fast.
Under the hood, “quasar dev” ends up calling “npm run dev”. It’s safe if you want to simply run “npm run dev” or “npm run build”.
Quasar CLI on the other hand does some extra work, checking if dev port is available (just to name one of those extra things).