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.

Holding back projects due to old version of GraphQL

See original GitHub issue

GraphQL is now at 15.4.0 but this project is holding things back at 14.7.0

Issue Analytics

State:
Created 3 years ago
Comments:8

Top GitHub Comments

1reaction

robross0606commented, May 4, 2022

Do you expect that the newer graphql-js version (v16.4.0) introspection query will be incompatible with older server versions of GraphQL?

I wouldn’t think so. Only the reverse is true.

I assume this error is coming from using a local schema file which the older graphql-js version doesn’t know how to parse properly?

That’s correct. I’m running against a locally parsed schema file.

0reactions

NathanRSmithcommented, May 5, 2022

Thanks again for your help. I believe v4.0.1 resolves this issue.

Top Results From Across the Web

GraphQL Best Practices

The GraphQL type system allows for some fields to return lists of values, but leaves the pagination of longer lists of values up...

Whole API versioning · Issue #175 · graphql/graphql-spec

Without versioning, when the behavior of an existing field needs to change, it is necessary to deprecate the old field and add a...

Subscriptions - Apollo GraphQL Docs

Subscriptions are useful for notifying your client in real time about changes to back-end data, such as the creation of a new object...

Migrating Existing REST APIs to GraphQL | by Mahesh Haldar

Given GraphQL is quite a fresher in the realm of software development, a lot of people are not yet confident whether to write...

GraphQL vs. REST: A GraphQL Tutorial - Toptal

GET /users/:id/projects?include=tasks (for example) on the dashboard page so that the back-end appends all related tasks. It's common practice to add ...