-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
peer dependency confilct when creating projects using vue 2 on npm #7149
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
Comments
I have the same issue. We can't even install or build our projects anymore. |
Same problem here with initial install from vue-cli Node => v16.15.1 Generated package.json {
"name": "test",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint"
},
"dependencies": {
"core-js": "^3.8.3",
"vue": "^2.6.14",
"vue-router": "^3.5.1",
"vuex": "^3.6.2"
},
"devDependencies": {
"@babel/core": "^7.12.16",
"@babel/eslint-parser": "^7.12.16",
"@vue/cli-plugin-babel": "~5.0.0",
"@vue/cli-plugin-eslint": "~5.0.0",
"@vue/cli-plugin-router": "~5.0.0",
"@vue/cli-plugin-vuex": "~5.0.0",
"@vue/cli-service": "~5.0.0",
"@vue/eslint-config-standard": "^6.1.0",
"eslint": "^7.32.0",
"eslint-plugin-import": "^2.25.3",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^5.1.0",
"eslint-plugin-vue": "^8.0.3",
"sass": "^1.32.7",
"sass-loader": "^12.0.0",
"vue-template-compiler": "^2.6.14"
}
} Hope it will help |
Create an |
how to fix this issue? |
To solve this issue simply downgrade the version which is suggested by npm. For eg. npm ERR! code ERESOLVE Here it is saying Could not resolve dependency: So please update eslint version between >= 1.6.0 < 7.0.0 in package.json file and then run command npm install Thank you. |
Version
4.5.15
Reproduction link
github.com
Environment info
Steps to reproduce
Run
vue create project_name
to create a vue project and then choose vue 2. Then
cd project_name && npm update
What is expected?
Dependencies updated
What is actually happening?
Opening because #6270 is closed and I can't re-open it.
Workaround is from: #6270 (comment)
The text was updated successfully, but these errors were encountered: