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

Please update [email protected] and [email protected] [email protected] warns about peer dependency graphql #11507

Closed
JustFly1984 opened this issue Feb 2, 2019 · 16 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change

Comments

@JustFly1984
Copy link

If I'm npm i my app with [email protected] I have this dependency issues with gatsby sub-dependencies:

npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requiresa peer of graphql@^14.1.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^14.1.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^14.1.0 but none is installed. You must install peer dependencies yourself.

if I'm npm i my app with [email protected] I have next sub-dependency issues

npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.

current versions of this dependencies:
[email protected] - safe to update
[email protected] - safe to update
[email protected] - need to be tested

@sidharthachatterjee sidharthachatterjee added the type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change label Feb 4, 2019
@sidharthachatterjee
Copy link
Contributor

Thank you for reporting this, @JustFly1984

cc @freiksenet

@JustFly1984
Copy link
Author

@Timothy-Guyon
Copy link

I am having similar issues

npm install --save gatsby-plugin-typography
npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of @emotion/core@^10.0.5 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.

@pxlla
Copy link

pxlla commented Feb 10, 2019

I'm chiming in too...

npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.

@sirojinadias
Copy link

sirojinadias commented Feb 15, 2019

Similar problem :

npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.

@DewiEJ
Copy link

DewiEJ commented Feb 17, 2019

Similar problem

npm install --save node-sass gatsby-plugin-sass
npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.

@millette
Copy link
Contributor

We all see the same warnings, no need to keep repeating here, thanks.

@lakerphan4life
Copy link

Any solution found? I keep running into these issues when trying to create a gatsby project

@millette
Copy link
Contributor

Progressing in (either) #11512 and #11568

@thomasryu
Copy link

Any progress on this issue? babel-plugin-remove-graphql-queries not working properly breaks both my project's Jest tests and Storybook stories :(

@DSchau
Copy link
Contributor

DSchau commented Feb 26, 2019

@thomasryu could you explain how this breaks functionality? This is a warning--it shouldn't impact underlying functionality.

@thomasryu
Copy link

thomasryu commented Mar 1, 2019

@DSchau sorry for the delay. I've recently updated Gatsby in order to use useStaticQuery.

Before the update, I was already using the standard StaticQuery to load images into my components, and my jest tests (simple render tests) and Storybook stories were working fine.

After the update, it seems Gatsby is unable to remove GraphQL queries inside components after the update, the complain received is the following:

It appears like Gatsby is misconfigured. Gatsby related `graphql` calls are supposed to only be
evaluated at compile time, and then compiled away,. Unfortunately, something went wrong and the
query was left in the compiled code.

I am assuming this is a problem with babel-plugin-remove-graphql-queries.

@gatsbot
Copy link

gatsbot bot commented Mar 22, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Mar 22, 2019
@ramusbucket
Copy link

ramusbucket commented Mar 24, 2019

@JustFly1984 @Timothy-Guyon @pxlla, I'm on [email protected], [email protected] and still facing issues. Linked issue above by @millette; does not seem to solve my problems. Thank you guys for your hard work on this awesome project.

@ramusbucket
Copy link

ramusbucket commented Mar 24, 2019

Here are the steps I followed -
gatsby new hello-world
npm install
npm i gatsby-source-pg
added config for gatsby-source-pg in gatsby-config.js
gatsby develop

when I try to execute graphql query in playgroud (http://localhost:8000/___graphql), I get following errors -

"message": "Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results.",

But then in warning it also says - I dont have dupliacate graphql -

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] requires a peer of graphql@^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of prop-types@^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.11.3 || ^0.12.3 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

@gatsbot
Copy link

gatsbot bot commented Apr 4, 2019

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

@gatsbot gatsbot bot closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change
Projects
None yet
Development

No branches or pull requests