Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Installing with npm and vue3

See original GitHub issue

When installing using npm I end up like this:

$ npm i @vueuse/motion     
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: twindy-demo@0.3.0
npm ERR! Found: vue@3.0.5
npm ERR! node_modules/vue
npm ERR!   vue@"^3.0.5" from the root project
npm ERR!   peer vue@"^2.0.0 || >=3.0.0-rc.0" from @vueuse/motion@1.0.0
npm ERR!   node_modules/@vueuse/motion
npm ERR!     @vueuse/motion@"*" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@">= 2.5 < 3" from @vue/composition-api@1.0.0-rc.2
npm ERR! node_modules/@vue/composition-api
npm ERR!   peer @vue/composition-api@">=1.0.0-rc.1" from @vueuse/motion@1.0.0
npm ERR!   node_modules/@vueuse/motion
npm ERR!     @vueuse/motion@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/dirk/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/dirk/.npm/_logs/2021-02-22T15_35_15_422Z-debug.log

My projects dependencies are:

"dependencies": {
    "twindy": "^0.11.0",
    "twindy-headless": "^0.8.0",
    "vue": "^3.0.5",
    "vue-i18n": "^9.0.0-rc.7",
    "vue-router": "^4.0.3"
  },
  "devDependencies": {
    "@types/node": "^14.14.31",
    "@vitejs/plugin-legacy": "^1.3.1",
    "@vitejs/plugin-vue": "^1.1.4",
    "@vue/compiler-sfc": "^3.0.5",
    "@vuedx/typecheck": "^0.6.3",
    "@vuedx/typescript-plugin-vue": "^0.6.3",
    "markdown-it-anchor": "^7.0.2",
    "markdown-it-prism": "^2.1.4",
    "stylus": "^0.54.8",
    "typescript": "^4.1.5",
    "vite": "^2.0.1",
    "vite-plugin-md": "^0.5.1",
    "vite-plugin-pwa": "^0.5.3"
  }

Maybe a npm issue due to conditions like "^2.0.0 || >=3.0.0-rc.0"?