Moved graphql to a peer-dependency

[Siyfion]

Also updated the dependency to the latest release of graphql.

[helfer]

I think with npm 3 you also have to make it a devDependency to make sure it gets installed for the tests.

[Siyfion]

That would explain why one environment fails and the other succeeds!

[Siyfion]

@helfer There you go, that should do it 👍

[helfer]

@Siyfion can we make the peer dependency accept a range like in graphql-tools? That way this change can be completely non-breaking.

[Siyfion]

@helfer Shall I leave the minimum on 0.7.x (previous dependency) or .5 / .6 like graphql-tools?

EDIT: Looking back I can see it did support v0.6.x at one point, but v0.5.x seems completely untested (so I've gone with 0.6.0 upwards).

[helfer]

Minimum should be what we had before, because I don't know if it will work with 0.6

[Siyfion]

Ah okay... 0.7.0 minimum it is!

[helfer]

@Siyfion thanks, awesome! I'll release a new version in the next few hours.

[helfer]

nvm, I already published it 😁

[Siyfion]

Awesome! Thanks for the help @helfer!

[Urigo]

#23

[dotansimha]

Awesome!! Thanks!!