Apollo-server: Update graphql dependency to 0.13

Created on 8 Feb 2018  路  11Comments  路  Source: apollographql/apollo-server

We cannot use latest graphql with apollo server. When will you update graphql dependency from 0.11.7 to latest version? 0.13.0 is now in npm repo.

Most helpful comment

Slightly curious how Apollo Engine and Apollo Client move forward with support (graphql 12+ etc) but this library doesn't update. Is apollo-server-express not the recommended/popular server any longer?

More just curious if users have transitioned to a newer server base I should be aware of, not trying to complain at all!

I also haven't noticed any issues yet by staying on 0.11.7 but didn't want to dive in if this was about to be updated properly by the Apollo team. Otherwise I can debug and submit a pull request.

All 11 comments

So graphql v0.13.0 works for me after a bit of work but the error messages were a bit nonsensical. Just adding my 2 cents to help others.

My app wasn't working, but thanks to this issue report I reverted to 0.11.7, which then gave me a useful error and I was able to debug my app. I then rolled forward again to 0.13.0 and it worked. I did get the below warning messages in 0.13.0 that I didn't get in 0.11.7

(node:63446) [DEP0016] DeprecationWarning: 'GLOBAL' is deprecated, use 'global'
(node:63446) [DEP0016] DeprecationWarning: 'root' is deprecated, use 'global'
(node:63446) [DEP0003] DeprecationWarning: _writeableState.buffer is deprecated, use _writeableState.getBuffer instead

This is using Node 8.9.4. Once I had debugged my app in 0.11.7 and rolled forward to 0.13.0 these messages disappeared.

Slightly curious how Apollo Engine and Apollo Client move forward with support (graphql 12+ etc) but this library doesn't update. Is apollo-server-express not the recommended/popular server any longer?

More just curious if users have transitioned to a newer server base I should be aware of, not trying to complain at all!

I also haven't noticed any issues yet by staying on 0.11.7 but didn't want to dive in if this was about to be updated properly by the Apollo team. Otherwise I can debug and submit a pull request.

@sbrichardson hey thanks for the comment -

Actually we updated to 0.12 already, just didn't do a good job with the messaging around it. This week @abernix and I are going to go through and make sure to merge all the PRs and close some old issues.

We're planning on putting a lot more time into the server moving forward, and would really appreciate some help! We'll try to handle the update to 0.13 ASAP, but if you want to go through and help us review some issues or PRs that would be much appreciated!

@stubailo hey, any news with this one or any chance to release a new version of apollo-server-core with 0.13 support?

It feels bad when every time you add a package you see this:

screen shot 2018-03-23 at 20 09 34

@vladshcherbin Yes, this is coming on Monday!

@abernix great news, thank you! :)

Thanks for updating. Peer deps still outdated in downstream packages, though (apollo-cache-control, apollo-tracing, graphql-extensions).

@transcranial That's correct.

For those that didn't notice already (as the observant @transcranial has! 馃槃) the apollo-server-* packages have been updated with a peerDependencies range supporting [email protected]. This are in place on the apollo-server-*@1.3.3 packages.

The other packages will be updated and published tomorrow morning after I've completed testing on them!

Thanks for linking to those @vladshcherbin.

And yes, I thought it made sense to leave this issue open until all those packages were updated, since the warnings will still persist in one form or other (even though the warnings don't stem from apollo-server-* packages anymore) until all those dependencies were done.

As of apollo-server-*@1.3.3 (released this past Monday, as noted in https://github.com/apollographql/apollo-server/issues/812#issuecomment-376260520 above), the peer dependency range for graphql has been expanded to include [email protected] (including the latest [email protected] which came out a couple weeks ago).

Additionally, as a stretch goal of this issue, the following transitive dependencies have also been updated, hopefully quelling all peer dependency warnings for graphql. It's worth noting that despite the previously-issued peer dependency warnings for graphql, the 0.13.x package has been known to be completely functional in all these packages, but hopefully this instills a bit more confidence:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

danilobuerger picture danilobuerger  路  3Comments

dupski picture dupski  路  3Comments

jpcbarros picture jpcbarros  路  3Comments

espoal picture espoal  路  3Comments

veeramarni picture veeramarni  路  3Comments