Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to install graphql-tools using npm and getting an error - No matching version found for @graphql-tools/utils@^8.6.2. #2084

Closed
Tracked by #2651 ...
vishnukavach opened this issue Feb 24, 2022 · 2 comments

Comments

@vishnukavach
Copy link

Describe the bug

Trying to install graphql-inspector using npm and getting an error:

$npm install @graphql-inspector/cli
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @graphql-tools/utils@^8.6.2.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kvishnu/.npm/_logs/2022-02-24T16_55_08_473Z-debug.log

To Reproduce
Steps to reproduce the behavior:

npm install @graphql-inspector/cli@latest

Expected behavior
Expected to install the library

Environment:

  • OS: Mac
  • NodeJS: v12.22.6

Additional context
graphql-tools/utils@^8.6.2 released
https://github.com/ardatan/graphql-tools/releases/tag/%40graphql-tools%2Futils%408.6.2

Able to install Previous release

$npm i @graphql-tools/utils@^8.6.1 
npm WARN [email protected] requires a peer of @grpc/proto-loader@^0.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No license field.
npm WARN The package @types/express is included as both a dev and production dependency.

+ @graphql-tools/[email protected]
added 1 package from 1 contributor and audited 1979 packages in 10.375s
@TuvalSimha
Copy link
Collaborator

@vishnukavach
I was tried to reproduce it, and all working just fine. Did you still have this issue?

@vishnukavach
Copy link
Author

yes @TuvalSimha It is working fine now, The issue occurred long back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants