Skip to content
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

@vue/apollo-composable@4.0.1 has a peer dependency conflict with Vue 3 #1535

Open
Soviut opened this issue Feb 11, 2024 · 5 comments
Open

@vue/apollo-composable@4.0.1 has a peer dependency conflict with Vue 3 #1535

Soviut opened this issue Feb 11, 2024 · 5 comments

Comments

@Soviut
Copy link

Soviut commented Feb 11, 2024

Describe the bug

I am using Vue 3 (vue@3.4.18) in my project. When upgrading to @vue/apollo-composable@4.0.1 I got the following peer dependency error saying Vue 3 was causing a peer dependency conflict that expected Vue 2.

npm ERR! While resolving: vite-vue3-template@0.0.0
npm ERR! Found: @vue/apollo-composable@4.0.0-beta.8
npm ERR! node_modules/@vue/apollo-composable
npm ERR!   @vue/apollo-composable@"4.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @vue/apollo-composable@"4.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vue@3.4.18
npm ERR! node_modules/vue
npm ERR!   peer vue@">= 2.5 < 2.7" from @vue/composition-api@1.7.2
npm ERR!   node_modules/@vue/composition-api
npm ERR!     peerOptional @vue/composition-api@"^1.0.0" from @vue/apollo-composable@4.0.1
npm ERR!     node_modules/@vue/apollo-composable
npm ERR!       @vue/apollo-composable@"4.0.1" from the root project

To Reproduce
Steps to reproduce the behavior:

  1. Create a vue 3 project
  2. npm install @vue/apollo-composable@4.0.0-beta.8
  3. update with npm install @vue/apollo-composable@4.0.1
  4. See peer dependency error

Expected behavior

I should be able to update without conflicts with Vue 3 and without having to force the install.

Versions
vue: 3.4.18
vue-apollo: 4.0.1
@apollo/client: 3.8.1

Additional context

My workaround was to to use the --force flag.

@peteluffman
Copy link

Same here

@msmosavar
Copy link

Same with vue 3.3.4 and @vue/apollo-composable 4.0.2

@nickmessing
Copy link
Member

Did you install @vue/composition-api? It shouldn't be installed and is correctly marked as optional in package.json, you should not get that error unless you also install @vue/composition-api

@msmosavar
Copy link

Did you install @vue/composition-api? It shouldn't be installed and is correctly marked as optional in package.json, you should not get that error unless you also install @vue/composition-api

No... here's my dependency list:

  "dependencies": {
    "@apollo/client": "^3.7.17",
    "@types/lodash": "^4.14.196",
    "@types/sortablejs": "^1.15.7",
    "@vue/apollo-composable": "^4.0.0-beta.8",
    "@vueuse/core": "^9.13.0",
    "ant-design-vue": "^3.2.13",
    "echarts": "^5.4.3",
    "element-plus": "^2.3.8",
    "graphql": "^15.7.2",
    "graphql-tag": "^2.12.6",
    "lodash": "^4.17.21",
    "sortablejs": "^1.15.1",
    "vue": "^3.3.4",
    "vue-echarts": "^6.6.0",
    "vue-i18n": "^9.2.2",
    "vue-router": "^4.2.4",
    "vuedraggable": "^4.1.0"
  },
  "devDependencies": {
    "@4tw/cypress-drag-drop": "^2.2.5",
    "@types/jest": "^27.4.0",
    "@typescript-eslint/eslint-plugin": "^5.62.0",
    "@typescript-eslint/parser": "^5.62.0",
    "@vicons/antd": "^0.12.0",
    "@vicons/carbon": "^0.12.0",
    "@vicons/fa": "^0.12.0",
    "@vicons/fluent": "^0.12.0",
    "@vicons/material": "^0.12.0",
    "@vitejs/plugin-vue": "^5.0.4",
    "@vue/eslint-config-standard": "^8.0.1",
    "@vue/eslint-config-typescript": "^11.0.3",
    "@vue/test-utils": "^2.4.1",
    "autoprefixer": "^10.4.14",
    "cypress": "^13.6.6",
    "eslint": "^8.57.0",
    "eslint-plugin-import": "^2.28.0",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^6.1.1",
    "eslint-plugin-standard": "^4.0.0",
    "eslint-plugin-vue": "^9.24.0",
    "postcss": "^8.4.27",
    "start-server-and-test": "^2.0.3",
    "tailwindcss": "^3.3.3",
    "typescript": "^5.1.6",
    "vite": "^5.1.3",
    "vite-plugin-html": "^3.2.2"
  }

@scq
Copy link
Contributor

scq commented Nov 19, 2024

Deleting package-lock.json and running npm install resolved this for me.

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

No branches or pull requests

5 participants