Issue with hot reloading

[blackxored]

If I edit a resolver twice it seems to blow up:

[GraphqlSchemaHot]: GraphQL Schema files was changed. Run rebuild...
(node:59825) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Schema must be an instance of GraphQLSchema. Also ensure that there are not multiple versions of GraphQL installed in your node_modules directory.
(node:59825) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I've enabled hot reload for my schema entrypoint file and this seems to be the culprit.
I'd love some pointers.

[nodkz]

I suppose you are using yarn and it blows up your node_modules folder when you made packages upgrades.

2 way to fix:

• completely remove node_modules folder and install all from scratch
• or go to node_modules/webpack-plugin-graphql-schema-hot/node_modules/ and remove graphql-js package from there

---

Keep this issue open. Must be implemented handling of this error - better console.log and catching promise rejection.

[blackxored]

I’m using lerna with `—hoist`, could that be it?

…

-- Best Regards, Adrian Perez https://adrianperez.codes

On September 13, 2017 at 10:05:00 AM, Pavel Chertorogov ( ***@***.***) wrote: I suppose you are using yarn and it blows up your node_modules folder when you made packages upgrades. 2 way to fix: - completely remove node_modules folder and install all from scratch - or go to node_modules/webpack-plugin-graphql-schema-hot/node_modules/ and remove graphql-js package from there ------------------------------ Keep this issue open. Must be implemented handling of this error - better console.log and catching promise rejection. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIIvB6JY5CbAPPFNp1pO1q91isrEduXks5sh4ysgaJpZM4PTvsX> .

[nodkz]

I added graphql@0.11 to peerDependencies it may solve your problem, may not. Please try 0.0.7.

Anyway, it looks like your package manager installs graphql-js several times. And your schema was build from one graphql package but this plugin uses another graphql package.