Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Latest version v14.1.0 breaks react-apollo and apollo-boost
See original GitHub issueI have upgraded to latest version of GraphQL v14.1.0 and my build won’t work after that. It fails to require react-apollo and apollo-boost.
Version 14.0.2 works fine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Apollo Boost migration - Apollo GraphQL Docs
Switch to the latest stable version. Apollo Boost migration. Learn how to set up Apollo Client manually without Apollo Boost. Apollo Boost is...
Read more >graphql-anywhere | Yarn - Package Manager
To get started with the React integration, go to our React Apollo ... project child package changes that were bundled into a specific...
Read more >apollo-boost - npm
The easiest way to get started with Apollo Client. Latest version: 0.4.9, last published: 3 years ago. Start using apollo-boost in your ...
Read more >Giving React + GraphQL a Lift with Apollo-Boost | by Jeff Lowery
I'll use the GraphQL server settings provided in the Apollo Client installation instructions. import ApolloClient from "apollo-boost"; const client = new ...
Read more >Consuming an Apollo GraphQL Server using React
To be able to query an Apollo server we need to do three things: Write our gql query; Utilize the Query component the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@langpavel hehe yeah I know, my yarn.lock can be evil some times.
@IvanGoncharov That makes sense, thank you.
@pitops You probably had two different versions of
graphql-jsin yournode_modules. This could happen if one of dependencies depend ongraphqlas direct dependency and not aspeerDependency. You can test it usingnpm lsand should see only one version ofgraphql.