@quasar/app - 1.4.1 - My app no longer builds (errors included)
See original GitHub issueThe newest app release broke quasar for me. (Windows 10)
quasar dev
Dev mode.......... spa
Pkg quasar........ v1.5.9
Pkg @quasar/app... v1.4.1
Debugging......... enabled
app:quasar-conf Reading quasar.conf.js +0ms
app:dev Checking listening address availability (0.0.0.0:8080)... +6ms
app:webpack Extending SPA Webpack config +899ms
app:generator Generating Webpack entry point +11ms
app:dev-server Booting up... +12ms
… and then …
ERROR Failed to compile with 32 errors 3:18:09 PM
error in ./src/pages/ComputeResources.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):
Vue packages version mismatch:
- vue@2.6.10 (F:\...\client\node_modules\vue\dist\vue.runtime.common.js)
- vue-template-compiler@2.6.11 (F:\...\client\node_modules\vue-template-compiler\package.json)
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using vue-loader@>=10.0, simply update vue-template-compiler.
If you are using vue-loader@<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.
@ ./src/router/routes.js 50:13-49
@ ./src/router/index.js
@ ./.quasar/app.js
@ ./.quasar/client-entry.js
@ multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
And tons of the exact same error description as above repeated for all of my components. And a good portion of the time there is another error:
error in ./src/pages/Support.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
- parse.js:14 parse
[client]/[@vue]/component-compiler-utils/dist/parse.js:14:23
- index.js:67 Object.module.exports
[client]/[vue-loader]/lib/index.js:67:22
@ ./src/router/routes.js 80:13-40
@ ./src/router/index.js
@ ./.quasar/app.js
@ ./.quasar/client-entry.js
@ multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
I work with Quasar every day. Let me know how and if I can help test. I tried “quasar clean” but it didn’t seem to help. Regressed to 1.4.0 and everything is fine again.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
[Solved]core-js issue | Quasar Framework Community
Hit “Y”, redid update with errors: @quasar/app: Missing. ... I'm stuck now with the same issue, since Quasar does not build my app...
Read more >Why does quasar not build my app when I ... - Stack Overflow
i am new to quasar, so i was trying to build the app to get the dist file but it stops compiling at...
Read more >Quasar Vue.js Tutorial - Let's Build An App! - YouTube
Quasar is an amazing Vue.js framework that makes it extremely easy to create responsive, SPA and fast apps. In this video I create...
Read more >Porting Quasar v.17 to v1.2 - Medium
Learn how to port your Quasar v.17 projects to v1.2. ... Boot files fulfill one special purpose: they run code before the App's...
Read more >Blog - Apache Cordova
By passing down all attribute data, Cordova-Common no longer needs to be ... In the Cordova app's package.json file, add the following:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@pdanpdan
I do NOT have any Vue dependencies in my package.json.I ran “npm prune” and still have the same result.For posterity I did find the culprit using this command…
npm ls vue@2.6.10Removed it (I wasn’t using it) and all good now. I never suspected a library would pull in a core Vue library. @pedrodgcouto perhaps this will help you.Thanks @rfox12 - I’m getting the same
TypeError: Cannot read property 'parseComponent' of undefinedand this seems to be the issue for me as well. Any thoughts on a workaround? I can’t get rid of the three libraries that all appear to be referencingvue@2.6.10