After making a new project with 15.14 cli I still see the vue plugin and it looks like my upgraded project is now consistent with this. So all is good and it does seem that @rstoenescu is still using the vue plugin which makes sense since it was supposed to replace the older html plugin for vue files and there must be something to help estlint with vue files. So bottom line the html plugin is deprecated and one should remove it from dev-dependencies and .eslintrc.
As to atom make sure the linter-eslint settings now turn off the html plugin option and that the scopes include text.html.vue
BTW my quasar.config.js build was fine, identical to above.
The project you cloned runs on an older version of Quasar, maybe the problem lies there? Try to create a new project with the latest version and see if the command line still hangs forever: http://quasar-framework.org/guide/index.html
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.