Error: Must provide Source. Received: undefined after upgrade to [email protected]

[Fi1osof]

Title.

Downgrade to [email protected] solve problem.

[ssypi]

Same here, it's possible the problem is in graphql-tools instead though as it seems to begin from there.

Error: Must provide Source. Received: undefined.
    at devAssert (node_modules/graphql/jsutils/devAssert.js:13:11)
    at new Parser (node_modules/graphql/language/parser.js:82:67)
    at Object.parse (node_modules/graphql/language/parser.js:35:16)
    at Object.<anonymous> (node_modules/graphql-tools/dist/stitching/introspectSchema.js:39:42)

---

at graphql-tools/dist/stitching/introspectSchema.js:39:42

var graphql_1 = require("graphql");
var linkToFetcher_1 = require("./linkToFetcher");
var parsedIntrospectionQuery = graphql_1.parse(graphql_1.introspectionQuery);

---

It seems that the bolded part graphql_1.introspectionQuery is undefined which then causes the error at node_modules/graphql/language/parser.js:82:67)

If I change that line from graphql_1.introspectionQuery -> graphql_1.getIntrospectionQuery() it seems to work.

---

EDIT: Ah, it's deprecated, mentioned in the changelogs:
#2124 Remove deprecated 'introspectionQuery' constant (@IvanGoncharov)

[yaacovCR]

Should be fixed in graphql-tools v4.0.7. (https://github.com/apollographql/graphql-tools/blob/master/CHANGELOG.md)

Which version are you using?

[ssypi]

I

Should be fixed in graphql-tools v4.0.7. (https://github.com/apollographql/graphql-tools/blob/master/CHANGELOG.md)

Which version are you using?

I was on latest v5 alpha, I’ll try latest stable tomorrow.

[mike-marcacci]

This is almost certainly due to the existence of multiple different versions of graphql in your dependency tree. You can look for this by running either:

# using yarn
yarn why graphql

# using npm
npm ls graphql

While GraphQL 15 is a major change, you may find that the libraries you use that have a stated dependency of 14 will still work with the new version. If this is the case, you can force the use of version 15 everywhere using yarn's resolutions or npm-force-resolutions.

However, the real solution is to make sure all libraries are updated to use the newest version of graphql.

[ssypi]

I

Should be fixed in graphql-tools v4.0.7. (https://github.com/apollographql/graphql-tools/blob/master/CHANGELOG.md)
Which version are you using?

I was on latest v5 alpha, I’ll try latest stable tomorrow.

Maybe op has a different problem, but for me at least, the problem seems to be in graphql-tools v5.0.0-alpha.2, downgrading to 4.0.7 fixed the problem.

[yaacovCR]

Should definitely be fixed in graphql-tools alpha.

One thing you can try is to delete your node_modules folder and reinstall:

Of note, this path is no longer within the graphql-tools alpha version:
node_modules/graphql-tools/dist/stitching/introspectSchema.js

Having been replaced by:
node_modules/graphql-tools/dist/stitch/introspectSchema.js

[ssypi]

Should definitely be fixed in graphql-tools alpha.

One thing you can try is to delete your node_modules folder and reinstall:

Of note, this path is no longer within the graphql-tools alpha version:
node_modules/graphql-tools/dist/stitching/introspectSchema.js

Having been replaced by:
node_modules/graphql-tools/dist/stitch/introspectSchema.js

I removed node_modules and package-lock.json several times during testing and the problem always reoccurred, but I think I found the problem.

There's a version 5.0.0-rc.1 published a year ago in NPM registry and it seems that for some reason npm was installing that version instead. I guess it thought it was newer than the 5.0.0-alpha.2. I had ^5.0.0-alpha.2 in my package.json.

This is a part of the package.json from graphql-tools that was getting installed and it seems to be the wrong version:

"_from": "graphql-tools@^5.0.0-alpha.2",
"_id": "[email protected]",
"version": "5.0.0-rc.1"

[yaacovCR]

Ahah, makes sense now, thanks!

That is a very old rc, and graphql-tools has gone back to alphas prior to release of v5.

[IvanGoncharov]

@yaacovCR Thanks investigating this issue 👍
It looks like nothing should be changed in graphql-js so I'm closing it.

[damiangreen]

I've bumped to the latest "graphql-tools": "^6.0.6", + "graphql": "15.0.0", and i still receive this error.
What is the resolution?

[yaacovCR]

Does @mike-marcacci comment above give and additional info: #2503 (comment)

[damiangreen]

I don't have multiple graphql versions

[jean9696]

I don't have multiple graphql versions

Same here 😕

[yaacovCR]

So far from above the problem seems to be with graphql-tools rather than graphql-js...

You might want to open an issue there with attention to version of graphql-tools. A minimal reproduction would be helpful.

[damiangreen]

ok i raised an issue there

[ahelord]

this repo example fail Apollo federation migrate example

[a7ul]

I had the same issue after upgrading to graphql v15

 "graphql": "^15.1.0",
 "apollo-server-express": "^2.16.0"

After reading through comments, I added

"resolutions": {
   "graphql-tools": "4.0.7"
 }

Following this, deleted my node_modules and reinstalled using yarn install

And it fixed my issue

[zenz]

@a7ul Thanks! your solution works for me!

[himharsh1997]

thanks man it worked.

[VukDukic]

I ran npm audit fix --force to fix couple of other modules and that did the trick for graphql module issue. However, something else broker. It seems that I am not able to run [email protected] with gatsby-plugin-mdx. Back to the drawing board....

[pflugs30]

For anyone who happens to reach this thread from Googling and is using serverless-appsync-simulator for a local AppSync environment, I'd like to post my solution. I was getting this same error when trying to test my production code locally. It turned out that though I was sending the localhost url for my local GraphQL endpoint, I was also trying to send a fully authenticated request header. Rather, I needed to use a hardcoded header such as this:
Authorization:AWS4-HMAC-SHA256 IAMAuthorized

Once I used this Authentication header instead of a fully signed V4 request, my POST requests went through successfully. Cheers!

[BigBrosh]

Body must be a string. Received: undefined
I've received this error after upgrading to graphql v15.5.0
This issue was resolved after I've upgraded graphql-tools to ^4.0.7 version

@IvanGoncharov can this solution be mentioned somewhere in documentation? maybe some section about upgrading to v15?
coz I couldn't google this issue and I've found this thread only after checking pr for Source
I'm not the first person who receives this error after upgrading graphql so would be nice to have it somewhere

[AlvSovereign]

Installing the most recent version of graphql-tools fixed this error for me.

[narajaon]

Fixed my issue by updating merge-graphql-schemas