ProjectOpenSea / opensea-js

TypeScript SDK for the OpenSea marketplace
https://docs.opensea.io/reference
MIT License
2.28k stars 955 forks source link

Clean Install Errors #58

Closed j0xhn closed 3 years ago

j0xhn commented 3 years ago

Hi, been trying to execute a npm install --save opensea-js on a clean create-react-app repo, node version v15.3.0 gives me the following error. Any help appreciated

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: typescript@2.9.2
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.17.1
npm ERR!   node_modules/tsutils
npm ERR!     tsutils@"^3.17.1" from @typescript-eslint/eslint-plugin@4.8.1
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       peer @typescript-eslint/eslint-plugin@"^4.0.0" from eslint-config-react-app@6.0.0
npm ERR!       node_modules/eslint-config-react-app
npm ERR!         eslint-config-react-app@"^6.0.0" from react-scripts@4.0.1
npm ERR!         node_modules/react-scripts
npm ERR!       1 more (react-scripts)
npm ERR!     tsutils@"^3.17.1" from @typescript-eslint/typescript-estree@4.8.1
npm ERR!     node_modules/@typescript-eslint/typescript-estree
npm ERR!       @typescript-eslint/typescript-estree@"4.8.1" from @typescript-eslint/experimental-utils@4.8.1
npm ERR!       node_modules/@typescript-eslint/experimental-utils
npm ERR!         @typescript-eslint/experimental-utils@"4.8.1" from @typescript-eslint/eslint-plugin@4.8.1
npm ERR!         node_modules/@typescript-eslint/eslint-plugin
npm ERR!         1 more (eslint-plugin-jest)
npm ERR!       1 more (@typescript-eslint/parser)
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   typescript@"^2.6.2" from wyvern-js@3.2.0
npm ERR!   node_modules/wyvern-js
npm ERR!     wyvern-js@"git+https://github.com/ProjectOpenSea/wyvern-js.git#v3.2.1" from opensea-js@1.1.10
npm ERR!     node_modules/opensea-js
npm ERR!       opensea-js@"*" from the root project
npm ERR!   3 more (awesome-typescript-loader, tslint, typescript-eslint-parser)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1" from react-scripts@4.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"4.0.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/johnstorey/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/johnstorey/.npm/_logs/2021-02-01T21_32_08_352Z-debug.log
AmazingMuffin commented 3 years ago

Hi John, I hope you are doing weel and that I don't bother you. I ran in the very same problem today and it would be great if you could share with how do you have solved this problem ? Thank you a lot, Alain

j0xhn commented 3 years ago

@AmazingMuffin not sure I remember exactly which step fixed it, but my gut is to run a rm -rf node_modules and probably delete the package-lock.json and then use version 12 of node and re-install. I'd say try that and let me know how it goes.

AmazingMuffin commented 3 years ago

Thank you for your help @johndangerstorey I've tried your method but had no luck and it did not work. I ran again and again in conflict with dependencies for the opensea-js sdk, I was only able to install the OpenSea SDK with Node 8. But with node 8, my react app won't start. I'll search another way of integrating a NFT platform with my little app.

I don't like the idea to use old dependencies referred by the OpenSea SDK with Node 8, because some dependencies aren't supported anymore and have a few open issues. I feel it not very secure going this way.

j0xhn commented 3 years ago

makes sense. i'm working on a project right now to become a type of nft api -- looking for contributors also ;)

On Wed, Apr 7, 2021 at 2:40 AM AmazingMuffin @.***> wrote:

Thank you for your help @johndangerstorey https://github.com/johndangerstorey I've tried your method but had no luck and it did not work. I ran again and again in conflict with dependencies for the opensea-js sdk, I was only able to install the OpenSea SDK with Node 8. But with node 8, my react app won't start. I'll search another way of integrating a NFT platform with my little app.

I don't like the idea to use old dependencies referred by the OpenSea SDK with Node 8, because some dependencies aren't supported anymore and have a few open issues. I feel it not very secure going this way.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ProjectOpenSea/opensea-js/issues/58#issuecomment-814646767, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUGCJS5YHNTEIM7BUFCJZTTHP46PANCNFSM4W5R5VYQ .

-- 𓁟 John D. Storey 𓀠 *resume https://johndangerstorey.com/resume.pdf* | linkedin http://www.linkedin.com/pub/john-d-storey/29/734/875 | instagram http://instagram.com/johndangerstorey/ | twitter https://twitter.com/johnDanger_ | facebook https://www.facebook.com/johndangerstorey?ref=tn_tnmn

AmazingMuffin commented 3 years ago

I was able to install the OpenSea SDK by using yarn instead of NPM. Don't know seem like there is a problem for NPM in the latest version to build correctly the dependcy tree. So I was able to make my first call as early as today... For contributions, sure I will, but please take in consideration that I'm a beginner in coding all those things, I will surely learn a lot more than contribute :-)

j0xhn commented 3 years ago

Cool yeah send me an email to john at nft.org and let's keep the convo going, really want to start exploring ways to build bounties and other open source tooling into the project so all skill levels are welcome to contribute :)