Cannot build on server - "gatsby-plugin-mdx" threw an error while running the createSchemaCustomization #217

elbuendiscipulo · 2021-12-01T01:22:14Z

elbuendiscipulo
Dec 1, 2021

I get this error when building this starter kit on a server for production, I have tested the code on 3 different computers and it works locally on MacOS and Windows, however when on the server (Ubuntu) I cannot neither do yarn build or yarn develop.

 ERROR #11321  PLUGIN

"gatsby-plugin-mdx" threw an error while running the createSchemaCustomization lifecycle:

Cannot read properties of undefined (reading 'setParserPlugins')

  TypeError: Cannot read properties of undefined (reading 'setParserPlugins')

Im using:

[email protected]
Gatsby CLI version: 3.13.0
Gatsby version: 4.2.0

Same versions locally, macOs, as on server Ubuntu.

I suspect the error comes from this file https://github.com/Vagr9K/gatsby-advanced-starter/blob/master/themes/advanced/gatsby/gatsby-config.ts at line 95

Has anyone encountered the same error or any idea on how to solve it?

elbuendiscipulo · 2021-12-01T01:36:11Z

elbuendiscipulo
Dec 1, 2021
Author

I use these versions, same on server and local:
Gatsby version: 4.2.0
[email protected]
[email protected]
[email protected]
[email protected]

This issue talk about similar issue with another plugin together with "gatsby-plugin-mdx" but their solution was to upgrade the plugins and I already have higher version than they recommend.
gatsbyjs/gatsby#33677

4 replies

Vagr9K Dec 1, 2021
Maintainer

Since it works locally but fails on the server, I can only assume that your NodeJS/Yarn/npm versions on the server are what's causing the issue.

I'd say try upgrading them via nvm.

I suspect the error comes from this file master/themes/advanced/gatsby/gatsby-config.ts at line 95

Yes. That's the line where the plugin is loaded. But the error comes from the plugin itself not the configuration.

elbuendiscipulo Dec 1, 2021
Author

Thank you for the advice @Vagr9K, I checked the versions and they are very similar. I did try to install same versions as I have local (local-1) on the server, but I still get the same error.

Server
node v16.13.0
npm 8.1.0
Yarn 1.22.15

Local-1
node v16.11.0
npm 8.0.0
Yarn 1.22.17

Local-2
node v14.18.0
npm 6.14.15
Yarn 1.22.17

Server after change:
node 16.11.0
npm 8.0.0
Yarn 1.22.15

After changing versions of node and npm, I removed the node_modules folder and run yarn install, then yarn develop.

Yes I agree that the error is not in the configuration file, but I just thought it might be related to the plugin order or that the plugins that are used together with the "gatsby-plugin-mdx" might affect the plugin, that's why I included the file in the comment.

I dont think the issue is with the versions of NodeJS, Yarn or npm.

Here's the full error message, I dont know if something further down might give a clue.

sudo yarn develop
yarn run v1.22.15
$ gatsby develop
success open and validate gatsby-configs, load plugins - 6.820s
success onPreInit - 0.044s
success initialize cache - 0.475s
success copy gatsby files - 0.176s
success Compiling Gatsby Functions - 0.998s
success onPreBootstrap - 1.071s

 ERROR #11321  PLUGIN

"gatsby-plugin-mdx" threw an error while running the createSchemaCustomization lifecycle:

Cannot read properties of undefined (reading 'setParserPlugins')



  TypeError: Cannot read properties of undefined (reading 'setParserPlugins')
  
  - create-schema-customization.js:79 Object.createSchemaCustomization
    [foldername]/[gatsby-plugin-mdx]/gatsby/create-schema-customization.js:79:37
  
  - api-runner-node.js:430 runAPI
    [foldername]/[gatsby]/src/utils/api-runner-node.js:430:22
  
  - api-runner-node.js:581 Promise.catch.decorateEvent.pluginName
    [foldername]/[gatsby]/src/utils/api-runner-node.js:581:13
  
  - debuggability.js:384 Promise._execute
    [foldername]/[bluebird]/js/release/debuggability.js:384:9
  
  - promise.js:518 Promise._resolveFromExecutor
    [foldername]/[bluebird]/js/release/promise.js:518:18
  
  - promise.js:103 new Promise
    [foldername]/[bluebird]/js/release/promise.js:103:10
  
  - api-runner-node.js:579 
    [foldername]/[gatsby]/src/utils/api-runner-node.js:579:16
  
  - util.js:16 tryCatcher
    [foldername]/[bluebird]/js/release/util.js:16:23
  
  - reduce.js:166 Object.gotValue
    [foldername]/[bluebird]/js/release/reduce.js:166:18
  
  - reduce.js:155 Object.gotAccum
    [foldername]/[bluebird]/js/release/reduce.js:155:25
  
  - util.js:16 Object.tryCatcher
    [foldername]/[bluebird]/js/release/util.js:16:23
  
  - promise.js:547 Promise._settlePromiseFromHandler
    [foldername]/[bluebird]/js/release/promise.js:547:31
  
  - promise.js:604 Promise._settlePromise
    [foldername]/[bluebird]/js/release/promise.js:604:18
  
  - promise.js:649 Promise._settlePromise0
    [foldername]/[bluebird]/js/release/promise.js:649:10
  
  - promise.js:729 Promise._settlePromises
    [foldername]/[bluebird]/js/release/promise.js:729:18
  
  - async.js:93 _drainQueueStep
    [foldername]/[bluebird]/js/release/async.js:93:12
  

success createSchemaCustomization - 0.455s
success Checking for changed pages - 0.008s
success source and transform nodes - 1.637s
success building schema - 2.599s

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "excerpt" on type "Mdx".

If you don't expect "excerpt" to exist on the type "Mdx" it is most likely a typo.
However, if you expect "excerpt" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "excerpt" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "Mdx":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: themes/advanced/gatsby/gatsby-node.ts:101:44


 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "timeToRead" on type "Mdx".

If you don't expect "timeToRead" to exist on the type "Mdx" it is most likely a typo.
However, if you expect "timeToRead" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "timeToRead" and right now it is not used anywhere. Therefore Gatsby can't infer the type
and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "Mdx":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: themes/advanced/gatsby/gatsby-node.ts:101:44


 ERROR 

Error while processing query results:


 ERROR 

[
  GraphQLError [Object]: Cannot query field "excerpt" on type "Mdx".
      at Object.Field (/home/foldername/foldername/node_modules/graphql/validation/rules/FieldsOnCorrectTypeRule.js:48:31)
      at Object.enter (/home/foldername/foldername/node_modules/graphql/language/visitor.js:323:29)
      at Object.enter (/home/foldername/foldername/node_modules/graphql/utilities/TypeInfo.js:370:25)
      at visit (/home/foldername/foldername/node_modules/graphql/language/visitor.js:243:26)
      at validate (/home/foldername/foldername/node_modules/graphql/validation/validate.js:69:24)
      at GraphQLRunner.validate (/home/foldername/foldername/node_modules/gatsby/src/query/graphql-runner.ts:105:16)
      at GraphQLRunner.query (/home/foldername/foldername/node_modules/gatsby/src/query/graphql-runner.ts:174:39)
      at apply (/home/foldername/foldername/node_modules/gatsby/src/bootstrap/create-graphql-runner.ts:57:8)
      at wrappedGraphQL (/home/foldername/foldername/node_modules/gatsby/src/services/create-pages.ts:34:47)
      at getIndexListing (/home/foldername/foldername/themes/advanced/gatsby/utils/queries.ts:47:34)
      at Object.createPages (/home/foldername/foldername/themes/advanced/gatsby/gatsby-node.ts:101:44)
      at runAPI (/home/foldername/foldername/node_modules/gatsby/src/utils/api-runner-node.js:430:22)
      at Promise.catch.decorateEvent.pluginName
(/home/foldername/foldername/node_modules/gatsby/src/utils/api-runner-node.js:581:13)
      at Promise._execute (/home/foldername/foldername/node_modules/bluebird/js/release/debuggability.js:384:9)
      at Promise._resolveFromExecutor (/home/foldername/foldername/node_modules/bluebird/js/release/promise.js:518:18)
      at new Promise (/home/foldername/foldername/node_modules/bluebird/js/release/promise.js:103:10) {
    locations: [ [Object] ]
  },
  GraphQLError [Object]: Cannot query field "timeToRead" on type "Mdx".
      at Object.Field (/home/foldername/foldername/node_modules/graphql/validation/rules/FieldsOnCorrectTypeRule.js:48:31)
      at Object.enter (/home/foldername/foldername/node_modules/graphql/language/visitor.js:323:29)
      at Object.enter (/home/foldername/foldername/node_modules/graphql/utilities/TypeInfo.js:370:25)
      at visit (/home/foldername/foldername/node_modules/graphql/language/visitor.js:243:26)
      at validate (/home/foldername/foldername/node_modules/graphql/validation/validate.js:69:24)
      at GraphQLRunner.validate (/home/foldername/foldername/node_modules/gatsby/src/query/graphql-runner.ts:105:16)
      at GraphQLRunner.query (/home/foldername/foldername/node_modules/gatsby/src/query/graphql-runner.ts:174:39)
      at apply (/home/foldername/foldername/node_modules/gatsby/src/bootstrap/create-graphql-runner.ts:57:8)
      at wrappedGraphQL (/home/foldername/foldername/node_modules/gatsby/src/services/create-pages.ts:34:47)
      at getIndexListing (/home/foldername/foldername/themes/advanced/gatsby/utils/queries.ts:47:34)
      at Object.createPages (/home/foldername/foldername/themes/advanced/gatsby/gatsby-node.ts:101:44)
      at runAPI (/home/foldername/foldername/node_modules/gatsby/src/utils/api-runner-node.js:430:22)
      at Promise.catch.decorateEvent.pluginName
(/home/foldername/foldername/node_modules/gatsby/src/utils/api-runner-node.js:581:13)
      at Promise._execute (/home/foldername/foldername/node_modules/bluebird/js/release/debuggability.js:384:9)
      at Promise._resolveFromExecutor (/home/foldername/foldername/node_modules/bluebird/js/release/promise.js:518:18)
      at new Promise (/home/foldername/foldername/node_modules/bluebird/js/release/promise.js:103:10) {
    locations: [ [Object] ]
  }
]


 ERROR #11321  PLUGIN

"gatsby-theme-advanced" threw an error while running the createPages lifecycle:

Cannot query field "excerpt" on type "Mdx".

GraphQL request:16:9
15 |         }
16 |         excerpt
   |         ^
17 |         timeToRead,Cannot query field "timeToRead" on type "Mdx".

GraphQL request:17:9
16 |         excerpt
17 |         timeToRead
   |         ^
18 |         frontmatter {

   99 |
  100 |   // Get full post listing
> 101 |   const fullListing = await getIndexListing(graphql);
      |                       ^
  102 |
  103 |   // Iterate over posts
  104 |   fullListing.forEach((post, index) => {

File: themes/advanced/gatsby/gatsby-node.ts:101:23



  Error: Cannot query field "excerpt" on type "Mdx".
  GraphQL request:16:9
  15 |         }
  16 |         excerpt
     |         ^
  17 |         timeToRead,Cannot query field "timeToRead" on type "Mdx".
  GraphQL request:17:9
  16 |         excerpt
  17 |         timeToRead
     |         ^
  18 |         frontmatter {
  
  - queries.ts:31 processQueryResult
    /home/foldername/foldername/themes/advanced/gatsby/utils/queries.ts:31:11
  
  - queries.ts:49 getIndexListing
    /home/foldername/foldername/themes/advanced/gatsby/utils/queries.ts:49:10
  
  - gatsby-node.ts:101 async Object.createPages
    /home/foldername/foldername/themes/advanced/gatsby/gatsby-node.ts:101:23
  
  - api-runner-node.js:430 async runAPI
    [foldername]/[gatsby]/src/utils/api-runner-node.js:430:16
  

failed createPages - 0.672s
success createPagesStatefully - 0.675s
info Total nodes: 78, SitePage nodes: 3 (use --verbose for breakdown)
success Checking for changed pages - 0.004s
success write out redirect data - 0.008s
success Build manifest and related icons - 0.006s
success onPostBootstrap - 0.031s
info bootstrap finished - 20.643s
success onPreExtractQueries - 0.003s

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "body" on type "Mdx".

If you don't expect "body" to exist on the type "Mdx" it is most likely a typo.
However, if you expect "body" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "body" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add
 it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "Mdx":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: themes/advanced/src/templates/post/query.ts:10:7


 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "timeToRead" on type "Mdx".

If you don't expect "timeToRead" to exist on the type "Mdx" it is most likely a typo.
However, if you expect "timeToRead" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "timeToRead" and right now it is not used anywhere. Therefore Gatsby can't infer the type
and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "Mdx":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: themes/advanced/src/templates/post/query.ts:11:7


 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "excerpt" on type "Mdx".

If you don't expect "excerpt" to exist on the type "Mdx" it is most likely a typo.
However, if you expect "excerpt" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "excerpt" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "Mdx":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: themes/advanced/src/templates/post/query.ts:12:7

failed extract queries from components - 5.947s
success write out requires - 0.021s
success run static queries - 0.035s - 1/1 28.96/s
success run page queries - 0.038s - 1/1 26.49/s

Vagr9K Dec 1, 2021
Maintainer

Hmm. Strange. Haven't had an issue like this on my end.

I guess as a workaround you can build locally and deploy on the server until this gets fixed on gatsby-plugin-mdx's end.

elbuendiscipulo Dec 1, 2021
Author

Killing my droplet and making a new one magically solved it. But I tried for 2 days and several hours of attempts of reinstalling before, so weird...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Cannot build on server - "gatsby-plugin-mdx" threw an error while running the createSchemaCustomization #217

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Cannot build on server - "gatsby-plugin-mdx" threw an error while running the createSchemaCustomization #217

Uh oh!

Uh oh!

elbuendiscipulo Dec 1, 2021

Replies: 1 comment · 4 replies

Uh oh!

Uh oh!

elbuendiscipulo Dec 1, 2021 Author

Uh oh!

Vagr9K Dec 1, 2021 Maintainer

Uh oh!

elbuendiscipulo Dec 1, 2021 Author

Uh oh!

Vagr9K Dec 1, 2021 Maintainer

Uh oh!

elbuendiscipulo Dec 1, 2021 Author

elbuendiscipulo
Dec 1, 2021

Replies: 1 comment 4 replies

elbuendiscipulo
Dec 1, 2021
Author

Vagr9K Dec 1, 2021
Maintainer

elbuendiscipulo Dec 1, 2021
Author

Vagr9K Dec 1, 2021
Maintainer

elbuendiscipulo Dec 1, 2021
Author