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 graphql to 14.0.2 #1891

Closed
JustFly1984 opened this issue Oct 12, 2018 · 7 comments
Closed

Please update graphql to 14.0.2 #1891

JustFly1984 opened this issue Oct 12, 2018 · 7 comments
Assignees
Labels
Build Related to build issues GraphQL Related to GraphQL API issues

Comments

@JustFly1984
Copy link

I have a project, which renders React app to static files on build with react-static. It uses webpack 4 and Babel7 to compile source code to static and dynamic pages. Similar to gatsby.js
Currently I have an issue with aws-amplify dependency on graphql@0.13.0. I have installed graphql@14.0.2 as dependency to my project, but then I run npm ls graphql I see this:

$ npm ls graphql
/projects/project
└─┬ aws-amplify@1.1.6
  └─┬ @aws-amplify/api@1.0.17
    └── graphql@0.13.0

and I do not see my freshly installed 14.0.2. Then I try to run dev environment, I got errors:

Attempted import error: 'print' is not exported from 'graphql'.

I'm looking at node_modules/graphql/index.js and I see the export of print in index.js file, and the version is 14.0.2 in package.json, but for some reason webpack using aws-amplify's version of graphql.

Please make loose dependency on graphql or make it peer-dependency.

@powerful23 powerful23 added Build Related to build issues GraphQL Related to GraphQL API issues labels Oct 12, 2018
@wnkz
Copy link

wnkz commented Oct 17, 2018

0.13.0 also has a bug on IE11 graphql/graphql-js#1356

@pungggi
Copy link

pungggi commented Oct 31, 2018

I also had a problem with gatsby. I ended using "resolutions": { "graphql": "0.13.2" }, in my package.json with yarn

Yes i think, treating graphql as a peer-dependency solves a lot of problems like this ones

@JustFly1984
Copy link
Author

Is there any movement on this issue?

@JustFly1984
Copy link
Author

Hello, please update graphql dependency - it causes a lot of frustration.

@elorzafe elorzafe added investigating This issue is being investigated and removed investigating This issue is being investigated labels Mar 1, 2019
@jordanranz jordanranz added to-be-reproduced Used in order for Amplify to reproduce said issue and removed investigating This issue is being investigated labels Jun 4, 2019
@sammartinez sammartinez removed the to-be-reproduced Used in order for Amplify to reproduce said issue label Jun 18, 2019
@stale
Copy link

stale bot commented Jul 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Jul 25, 2019

This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems.

@stale stale bot closed this as completed Jul 25, 2019
@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Build Related to build issues GraphQL Related to GraphQL API issues
Projects
None yet
Development

No branches or pull requests

8 participants