-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarn run dev fails to build right after running init #995
Comments
The issue was solved. I locked vue-template-compiler to version 2.5.13 and rebuilt my yarn.lock file. After that everything ran smoothly. |
@dedward3 Hi, I'm not familiar working with yarn .I experienced this issue only I'm working with laravel. How did you lock vue-template-compiler and rebuilt it ? can you please guide me ? |
@abrhambas01 I went into my package.json file and made sure there were no '~' or '^' in front of vue-template-compiler. I also made sure my vue-template-compiler version matched all the other versions, and then ran 'yarn' and then 'yarn install'. |
In my package.json I don't have vue-template-compiler entry there but I have vue in there so what I'm thinking maybe when I do npm install, it pulled the latest version of vue-template-compiler that didn't matched my vue's version. |
Version
2.9.3
Reproduction link
https://medium.com/codingthesmartway-com-blog/vue-js-2-quickstart-tutorial-2017-246195cfbdd2
Steps to reproduce
OS -> Mac OS
Here's what I did/reproduction steps
Error Message:
Module build failed: Error:
Vue packages version mismatch:
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.
What is expected?
Vue build to be successful after having changed nothing in a fresh project.
What is actually happening?
Vue build is failing after having changed nothing in a fresh project.
I'm not trying to be a smart ass with my reproduction link. I will be hounded by our security team if I push things to github, and I don't know how else to show you what's going on. So I just linked the article that I was following.
The text was updated successfully, but these errors were encountered: