Quasar: @quasar/app - 1.4.1 - My app no longer builds (errors included)

Created on 14 Dec 2019  路  5Comments  路  Source: quasarframework/quasar

The 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:

- [email protected] (F:\...\client\node_modules\vue\dist\vue.runtime.common.js)
- [email protected] (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.

bug

Most helpful comment

@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 [email protected]
Removed 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.

All 5 comments

Same issue here. After upgrading to 1.4.1 everything breaks. Errors very similar to yours.

If you use npm first clean up node_modules.
Then check if you set vue-loader or vue-template-compiler by hand in package.json
And check this: https://github.com/quasarframework/quasar/issues/5886

By the way, the error is clear in the output - you have vue set to 2.6.10 in your package.json

@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 [email protected]
Removed 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

Thanks @rfox12 - I'm getting the same TypeError: Cannot read property 'parseComponent' of undefined and 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 referencing [email protected]

Was this page helpful?
0 / 5 - 0 ratings