tqtezos / minter

OpenMinter is dApp framework for enabling the creation and collection of non-fungible tokens (NFTs) on Tezos.
MIT License
192 stars 91 forks source link

Dependency conflict (unable to resolve dependency tree) #415

Closed ungarson closed 3 years ago

ungarson commented 3 years ago

Versions that I have: 0.7.0 of minter 7.11.1 of npm 12.16.1 of node

When I run npm install, I receive these errors:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: typescript@4.1.3
npm ERR! node_modules/typescript
npm ERR!   typescript@"4.1.3" from the root project
npm ERR!   peer typescript@">=2.7" from ts-node@9.1.1
npm ERR!   node_modules/ts-node
npm ERR!     dev ts-node@"9.1.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1" from react-scripts@3.4.1
npm ERR! node_modules/react-scripts
npm ERR!   dev react-scripts@"3.4.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.
npm ERR! 
npm ERR! See /Users/a2/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/a2/.npm/_logs/2021-05-05T18_59_01_310Z-debug.log

Neither npm install --legacy-peer-deps nor npm install --force do not work, I end up with this error

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/a2/WebstormProjects/minter/minter/node_modules/@tqtezos/minter-contracts/ts-node src/compile-ligo.ts
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/a2/WebstormProjects/minter/minter/node_modules/@tqtezos/minter-contracts/ts-node src/compile-ligo.ts'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/a2/.npm/_logs/2021-05-05T19_01_52_645Z-debug.log

Deleting node_modules and then running npm install does not work too.

Also, Support section in the README.md does not specify the required npm and node version, I guess it would be useful, since a lot of problems happen because of different node versions, and also since npm is suggested in the Quickstart section.

ungarson commented 3 years ago

It works if I run yarn

obstropolos commented 3 years ago

Removed option in documentation and cleaned up for the v0.7.1 release. Closing this for now until we bring back support if necessary.

ana723 commented 3 years ago

Thanks you