Closed Jkker closed 3 years ago
Hey @Jkker, what version of Node.js are you using?
I actually just updated the project to remove puppeteer as we really aren't using it, and it's a large, complicated dependency.
Please sync with latest and try again.
Thanks.
Hey @Jkker, what version of Node.js are you using?
I actually just updated the project to remove puppeteer as we really aren't using it, and it's a large, complicated dependency.
Please sync with latest and try again.
Thanks.
Thanks for the reply! I am using Node v15.13.0 alongside NPM 7.9.0.
Magically, Yarn (v1.22.5) magically resolves all these dependencies errors with only a few warnings. It works for both before and after your latest commit to remove puppeteer
from the deps. Unfortunately, npm i
still gives an error regarding React versions.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: nextjs-notion-starter-kit@0.1.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR! react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from use-dark-mode@2.3.1
npm ERR! node_modules/use-dark-mode
npm ERR! use-dark-mode@"^2.3.1" 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.
And running npm i --legacy-peer-deps
or npm i --force
still results in the same error when installing sharp
.
npm ERR! ../src/common.cc:23:10: fatal error: vips/vips8: No such file or directory
Which is identical to what's in my first comment.
I will try again later with a different version of npm.
Thanks!
This looks like an issue that's specific to your environment.
Feel free to add more info to this issue if you find a workaround, but otherwise I don't think we can really help, so going to close for now.
Thanks.
Running
npm install
after cloning this repository results in a dependency error:Attempting a work-around, I ran
npm install --force
and got thisRunning
npm install --legacy-peer-deps
produces an identical result.