erskingardner / nostr-how

https://nostr.how
112 stars 51 forks source link

Problem with executing the npm install command #193

Closed dbarabashh closed 4 months ago

dbarabashh commented 4 months ago

Hey, I've started translating to Ukrainian, but I ran into a few small blockers.

When installing npm packages, I got this error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: nostr-how@0.2.0
npm ERR! Found: eslint@9.5.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^9.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/parser@7.13.1
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"^7.9.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.13.1
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^7.9.0" 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! A complete log of this run can be found in:

Then I ran this command:

npm install --legacy-peer-deps

As a result, I got this error:

➜  nostr-how git:(ukrainian_translation) npm install --legacy-peer-deps
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: nostr-how@0.2.0
npm ERR! notsup Not compatible with your version of node/npm: nostr-how@0.2.0
npm ERR! notsup Required: {"node":">=18"}
npm ERR! notsup Actual:   {"npm":"8.19.3","node":"v16.19.1"}

But I fixed it by installing the correct version using nvm. To solve this issue, I would add a .nvmrc file.

Summary. Overall, this isn't blocking me, but I think the experience should be improved a bit for future contributors

/cc @erskingardner

erskingardner commented 4 months ago

The project uses pnpm instead of npm so you should use that instead.

dbarabashh commented 4 months ago

@erskingardner lol, sorry :)