Update graphql to the latest version 🚀

[greenkeeper]

Version 0.10.0 of graphql just got published.

Dependency	graphql
Current Version	0.9.6
Type	devDependency

The version 0.10.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of graphql.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Release Notes

v0.10.0

New

• Initial support for GraphQL subscriptions (#846).
• isValidValue() and isValidLiteral() added to Scalar and enum types (#861).
• You can now set a custom default field resolver (#865).
• graphql() may now take a Source object, in addition to the existing support for string (#866).
• graphql() may now take an object with named parameters (#867).

Breaking

• Spec compliance: forbid duplicate type definitions (#744).
• Spec compliance: disallow inappropriate coercion of non-Int values to Int (#837).

Fixes

• Ensure GraphQLError stack trace includes error message (#718).
• Fix input coercion to allow null-valued Enums as arguments (#848).
• Fix for fields that are JavaScript keywords (#864).
• Compatibility with Flow v0.47.0 (#878).

Commits

The new version differs by 57 commits.

• 797e7e3 0.10.0
• 845a45b Merge pull request #878 from gabelevi/flow
• fe5f544 Flow v0.47.0 finds 3 errors in master. This is important to fix, because the
• 87b24ee Freshen yarn.lock
• 704a97d Merge pull request #877 from graphql/greenkeeper/mocha-3.4.2
• 0f186de chore(package): update mocha to version 3.4.2
• 1ff4932 Freshen yarn.lock
• e989de8 Merge pull request #875 from graphql/greenkeeper/sane-1.7.0
• 9811d06 chore(package): update sane to version 1.7.0
• f6f26fd Handle abrupt closing in mapAsyncIterator() (#870)
• 50504b9 remove unnecessary null arguments in test
• 562cead Allow providing an object of arguments to graphql(). (#867)
• 1b41959 Allow graphql() to accept a Source instance. (#866)
• bf352a8 json is hard
• 5510c75 Allow providing custom default field resolver. (#865)

There are 57 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[mxstbr]

The only failing tests here are all the tests for this behaviour:

sends stack trace to error if in an error occurs and debug mode is set

@helfer any chance you know why this is happening and can point me towards a fix? Landing this update is important because otherwise it's impossible to use the new graphql-subscriptions and graphql-transport-ws with graphql-server-express since they rely on the graphql@0.10.x new subscriptions stuff! 😊

/cc @Urigo

[DxCx]

Replaced by #407