Skip to content
This repository has been archived by the owner on Dec 6, 2021. It is now read-only.

vue dependency version mismatch #192

Closed
Rayraegah opened this issue Jun 16, 2017 · 6 comments
Closed

vue dependency version mismatch #192

Rayraegah opened this issue Jun 16, 2017 · 6 comments

Comments

@Rayraegah
Copy link

Rayraegah commented Jun 16, 2017

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Breaks with following error

Error in ./app/app-root.vue
Module build failed: Error:
Vue packages version mismatch:

- vue@2.3.4
- vue-template-compiler@2.3.3

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.

If the current behavior is a bug, please provide the steps to reproduce.
Add latest version Vue as dependency and run script dev.

What is the expected behavior?
automatically fix version mismatch or disallow local npm dependency (always use vue version from poi's package.json)

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, Poi version and Operating System.
poi v9.0.2, node v8.1.1, npm v5

@Rayraegah
Copy link
Author

Rayraegah commented Jun 16, 2017

It only happens if you have vue as a dependency in project package.json and you bump its version.

If you run into this error and you can hard reset your repo after removing vue from your package.json dependencies

$ rm -rf node_modules
$ rm package-lock.json
$ npm install

to fix the error.

@egoist
Copy link
Owner

egoist commented Jun 16, 2017

If you want to use your own version of Vue, you need to install both vue and vue-template-compiler in your project since vue@version might mismatch poi/~/vue-template-compiler@version.

@Rayraegah
Copy link
Author

Got it. Thanks.

@egoist
Copy link
Owner

egoist commented Jun 16, 2017

Yeah, I might add a more detailed error message to the CLI output when this error occurs.

@egoist
Copy link
Owner

egoist commented Jun 16, 2017

This is how it will look like:

2017-06-16 10 20 58

@Rayraegah
Copy link
Author

Looks good imo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants