Duplicate “graphql” modules cannot be used

I have found that the graphql-js library does not allow dependencies to also use graphql.

You would get the following error

Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results.

from the following code

const express = require('express');
const graphqlHTTP = require('express-graphql');
const GraphQLSchema = require('graphql'); 
// the module graphql-test-mod-obj-type' has 
// graphql as a depenedency
const myType = require('graphql-test-mod-obj-type');

const app = express();

const schema = new GraphQLSchema( query: myType )

app.use('/graphql', graphqlHTTP(
 schema,
 graphiql: true
));

app.listen(4000);

I created a small repo and a small public npm package to demonstrate this
repo-with-npm-dependency-on-graphql .

This can be quite easily worked around by not having the graphql module as a dependency in the module. But surely this is an issue? Or is this a well known thing?

asked Nov 11 '18 at 19:24

Glenn Hinks

413

If NODE_ENV is set to production this check is not carried out. I'm not sure why we have this difference?

– Glenn Hinks
Nov 11 '18 at 22:05

add a comment |

I have found that the graphql-js library does not allow dependencies to also use graphql.

You would get the following error

from the following code

const express = require('express');
const graphqlHTTP = require('express-graphql');
const GraphQLSchema = require('graphql'); 
// the module graphql-test-mod-obj-type' has 
// graphql as a depenedency
const myType = require('graphql-test-mod-obj-type');

const app = express();

const schema = new GraphQLSchema( query: myType )

app.use('/graphql', graphqlHTTP(
 schema,
 graphiql: true
));

app.listen(4000);

I created a small repo and a small public npm package to demonstrate this
repo-with-npm-dependency-on-graphql .

This can be quite easily worked around by not having the graphql module as a dependency in the module. But surely this is an issue? Or is this a well known thing?

asked Nov 11 '18 at 19:24

Glenn Hinks

413

If NODE_ENV is set to production this check is not carried out. I'm not sure why we have this difference?

– Glenn Hinks
Nov 11 '18 at 22:05

add a comment |

I have found that the graphql-js library does not allow dependencies to also use graphql.

You would get the following error

from the following code

const express = require('express');
const graphqlHTTP = require('express-graphql');
const GraphQLSchema = require('graphql'); 
// the module graphql-test-mod-obj-type' has 
// graphql as a depenedency
const myType = require('graphql-test-mod-obj-type');

const app = express();

const schema = new GraphQLSchema( query: myType )

app.use('/graphql', graphqlHTTP(
 schema,
 graphiql: true
));

app.listen(4000);

I created a small repo and a small public npm package to demonstrate this
repo-with-npm-dependency-on-graphql .

This can be quite easily worked around by not having the graphql module as a dependency in the module. But surely this is an issue? Or is this a well known thing?

asked Nov 11 '18 at 19:24

Glenn Hinks

413

I have found that the graphql-js library does not allow dependencies to also use graphql.

You would get the following error

from the following code

const express = require('express');
const graphqlHTTP = require('express-graphql');
const GraphQLSchema = require('graphql'); 
// the module graphql-test-mod-obj-type' has 
// graphql as a depenedency
const myType = require('graphql-test-mod-obj-type');

const app = express();

const schema = new GraphQLSchema( query: myType )

app.use('/graphql', graphqlHTTP(
 schema,
 graphiql: true
));

app.listen(4000);

I created a small repo and a small public npm package to demonstrate this
repo-with-npm-dependency-on-graphql .

This can be quite easily worked around by not having the graphql module as a dependency in the module. But surely this is an issue? Or is this a well known thing?

graphql-js

asked Nov 11 '18 at 19:24

Glenn Hinks

413

asked Nov 11 '18 at 19:24

Glenn Hinks

413

asked Nov 11 '18 at 19:24

Glenn Hinks

413

asked Nov 11 '18 at 19:24

Glenn Hinks

413

asked Nov 11 '18 at 19:24

Glenn Hinks

413

If NODE_ENV is set to production this check is not carried out. I'm not sure why we have this difference?

– Glenn Hinks
Nov 11 '18 at 22:05

add a comment |

If NODE_ENV is set to production this check is not carried out. I'm not sure why we have this difference?

– Glenn Hinks
Nov 11 '18 at 22:05

If NODE_ENV is set to production this check is not carried out. I'm not sure why we have this difference?

– Glenn Hinks
Nov 11 '18 at 22:05

add a comment |

1 Answer
1

active

oldest

votes

it does appear that this is a longstanding and known issue and is covered here

answered Nov 12 '18 at 23:03

Glenn Hinks

413

add a comment |

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53252347%2fduplicate-graphql-modules-cannot-be-used%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

it does appear that this is a longstanding and known issue and is covered here

answered Nov 12 '18 at 23:03

Glenn Hinks

413

add a comment |

it does appear that this is a longstanding and known issue and is covered here

answered Nov 12 '18 at 23:03

Glenn Hinks

413

add a comment |

it does appear that this is a longstanding and known issue and is covered here

answered Nov 12 '18 at 23:03

Glenn Hinks

413

it does appear that this is a longstanding and known issue and is covered here

answered Nov 12 '18 at 23:03

Glenn Hinks

413

answered Nov 12 '18 at 23:03

Glenn Hinks

413

answered Nov 12 '18 at 23:03

Glenn Hinks

413

answered Nov 12 '18 at 23:03

Glenn Hinks

413

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Dfyjkt