search

paramander / contentful-rich-text-vue-renderer

Render Contentful Rich Text field using Vue
https://www.npmjs.com/package/contentful-rich-text-vue-renderer
MIT License
38 stars 12 forks source link

Dependency Tree issue #58

Open felixdenoix opened 9 months ago

felixdenoix commented 9 months ago

Issue

Encountered an error while trying to install package on project. The error prompted was the following one: 

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: project@undefined
npm ERR! Found: @contentful/rich-text-types@16.3.0
npm ERR! node_modules/@contentful/rich-text-types
npm ERR!   @contentful/rich-text-types@"^16.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @contentful/rich-text-types@"^15.14.1" from contentful-rich-text-vue-renderer@3.1.0
npm ERR! node_modules/contentful-rich-text-vue-renderer
npm ERR!   contentful-rich-text-vue-renderer@"*" 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.

Downgrading @contentful/rich-text-types to @^15 allowed me to install the package. After having a look to the changelog of the different rich-text related packages, it seems that the upgrade between 15 and 16 is only a version bump. Would you consider updating the dependencies on this package ?

Project Package.json

  "devDependencies": {
    "@nuxt/devtools": "^0.8.4",
    "@nuxt/image": "^1.0.0-rc.1",
    "@nuxt/kit": "npm:@nuxt/kit-edge@latest",
    "@nuxtjs/eslint-config-typescript": "^12.0.0",
    ...
  },
  "dependencies": {
    "@contentful/rich-text-html-renderer": "^16.0.2",
    "@contentful/rich-text-types": "^16.0.2",
    "@pinia/nuxt": "^0.4.3",
    "@studio-freight/lenis": "^1.0.22",
    "contentful": "^10.5.1",
    "gsap": "^3.10.2",
    "h3-zod": "^0.5.1",
    "rupture": "^0.7.1",
    "zod": "^3.22.2"
  }

Config

Darwin 22.6.0 node v18.18.0 npm v9.8.1

PS

Thanks for the package ✌️

perenstrom-bontouch commented 1 month ago

I don't think this should have been closed. This is still needed

felixdenoix commented 1 month ago

I closed the issue as it had no response in the first 6 months so i figured it must have been a cache issue on my package manager or whatnot but you are right the error is still present.