Subplugins loading doesn't respect `main` field in `package.json` #33677

pieh · 2021-10-26T11:05:30Z

I'm currently having issues in Gatsby 4 with my gatsby-remark-acronyms plugin that I never experienced before!

From what I can tell, the initial plugin validation is failing because my plugin entry point is under a "dist" folder instead of the root of the plugin (mind you, there is a "main" entry pointing on the plugin package.json, pointing to this file), but this works fine in Gatsby 2 and 3.

Repro is quite easy, I just created a new Gatsby site with gatsby new, only specification I added was to have markdown with MDX, and then run npm add gatsby-remark-acronyms.

On the gatsby-config.js I replaced this:

`gatsby-plugin-mdx`,

with this:

{
  resolve: `gatsby-plugin-mdx`,
  options: {
    gatsbyRemarkPlugins: [
      {
        resolve: `gatsby-remark-acronyms`,
        options: {
          acronyms: {
            API: 'Application Programming Interface',
            ASAP: 'As Soon As Possible'
          },
        },
      },
    ],
  },
},

When I run npm run build, this is what I got:

> [email protected] build D:\Projects\gatsby-test
> gatsby build

Error: Cannot find module 'D:/Projects/gatsby-test/node_modules/gatsby-remark-acronyms/index'
Require stack:
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bootstrap\load-plugins\validate.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bootstrap\load-plugins\load.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bootstrap\load-plugins\index.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bootstrap\load-config-and-plugins.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\services\initialize.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\services\index.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bootstrap\index.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\commands\build.js
- D:\Projects\gatsby-test\node_modules\gatsby-cli\lib\create-cli.js
- D:\Projects\gatsby-test\node_modules\gatsby-cli\lib\index.js
- D:\Projects\gatsby-test\node_modules\gatsby\dist\bin\gatsby.js
- D:\Projects\gatsby-test\node_modules\gatsby\cli.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
    at Function.resolve (D:\Projects\gatsby-test\node_modules\v8-compile-cache\v8-compile-cache.js:164:23)
    at D:\Projects\gatsby-test\node_modules\gatsby\src\bootstrap\load-plugins\validate.ts:234:52
    at Object.validate (D:\Projects\gatsby-test\node_modules\joi\lib\types\any.js:47:28)
    at Object.internals.rules (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:394:33)
    at Object.exports.validate (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:350:22)
    at internals.Base.$_validate (D:\Projects\gatsby-test\node_modules\joi\lib\base.js:773:26)
    at Object.validate (D:\Projects\gatsby-test\node_modules\joi\lib\types\array.js:273:45)
    at Object.internals.rules (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:394:33)
    at Object.exports.validate (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:350:22)
    at internals.Base.$_validate (D:\Projects\gatsby-test\node_modules\joi\lib\base.js:773:26)
    at Object.validate (D:\Projects\gatsby-test\node_modules\joi\lib\types\keys.js:108:45)
    at Object.exports.validate (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:325:26)
    at Object.internals.entry (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:142:28)
    at Object.exports.entryAsync (D:\Projects\gatsby-test\node_modules\joi\lib\validator.js:58:30)
    at internals.Base.validateAsync (D:\Projects\gatsby-test\node_modules\joi\lib\base.js:553:26) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bootstrap\\load-plugins\\validate.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bootstrap\\load-plugins\\load.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bootstrap\\load-plugins\\index.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bootstrap\\load-config-and-plugins.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\services\\initialize.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\services\\index.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bootstrap\\index.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\commands\\build.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby-cli\\lib\\create-cli.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby-cli\\lib\\index.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\dist\\bin\\gatsby.js',
    'D:\\Projects\\gatsby-test\\node_modules\\gatsby\\cli.js'
  ]
}
success open and validate gatsby-configs, load plugins - 0.852s
success onPreInit - 0.004s
success initialize cache - 0.080s
success copy gatsby files - 0.096s
success Compiling Gatsby Functions - 0.284s
success onPreBootstrap - 0.297s

 ERROR #11321  PLUGIN

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

Cannot read property 'setParserPlugins' of undefined



  TypeError: Cannot read property 'setParserPlugins' of undefined

  - create-schema-customization.js:79 Object.createSchemaCustomization
    [gatsby-test]/[gatsby-plugin-mdx]/gatsby/create-schema-customization.js:79:37

  - api-runner-node.js:430 runAPI
    [gatsby-test]/[gatsby]/src/utils/api-runner-node.js:430:22

  - api-runner-node.js:581 Promise.catch.decorateEvent.pluginName
    [gatsby-test]/[gatsby]/src/utils/api-runner-node.js:581:13

  - debuggability.js:384 Promise._execute
    [gatsby-test]/[bluebird]/js/release/debuggability.js:384:9

  - promise.js:518 Promise._resolveFromExecutor
    [gatsby-test]/[bluebird]/js/release/promise.js:518:18

  - promise.js:103 new Promise
    [gatsby-test]/[bluebird]/js/release/promise.js:103:10

  - api-runner-node.js:579
    [gatsby-test]/[gatsby]/src/utils/api-runner-node.js:579:16

  - util.js:16 tryCatcher
    [gatsby-test]/[bluebird]/js/release/util.js:16:23

  - reduce.js:166 Object.gotValue
    [gatsby-test]/[bluebird]/js/release/reduce.js:166:18

  - reduce.js:155 Object.gotAccum
    [gatsby-test]/[bluebird]/js/release/reduce.js:155:25

  - util.js:16 Object.tryCatcher
    [gatsby-test]/[bluebird]/js/release/util.js:16:23

  - promise.js:547 Promise._settlePromiseFromHandler
    [gatsby-test]/[bluebird]/js/release/promise.js:547:31

  - promise.js:604 Promise._settlePromise
    [gatsby-test]/[bluebird]/js/release/promise.js:604:18

  - promise.js:649 Promise._settlePromise0
    [gatsby-test]/[bluebird]/js/release/promise.js:649:10

  - promise.js:729 Promise._settlePromises
    [gatsby-test]/[bluebird]/js/release/promise.js:729:18

  - async.js:93 _drainQueueStep
    [gatsby-test]/[bluebird]/js/release/async.js:93:12


not finished createSchemaCustomization - 0.116s

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `gatsby build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\pedro\AppData\Roaming\npm-cache\_logs\2021-10-26T10_00_52_634Z-debug.log

The error makes sense, as there is no "gatsby-remark-acronyms/index", but I would expect it to respect the "main" entry and thus use "gatsby-remark-acronyms/dist/index".

Is this expected behavior or some kind of bug introduced in Gatsby 4?

Originally posted by @pedrolamas in #32860 (comment)

The text was updated successfully, but these errors were encountered:

akabekobeko · 2021-10-28T08:16:15Z

I'm having trouble with the same problem.

Gatsby v4 support? · Issue #34 · akabekobeko/npm-gatsby-remark-copy-relative-linked-files

Has it been changed to GatsbyJS v4 to ignore the main entry in package.json?

If this is a specification, plugin support is required, so please describe it in Migrating from v3 to v4. If it is a bug, please fix it.

j-e-clark · 2021-11-01T19:00:55Z

I've been trying to upgrade a site to Gatsby v4 and discovered the issue also affects gatsby-remark-relative-images.

Plugin uses "main": "dist/index.js", in package.json and is currently breaking v4 with the same error.

ehowey · 2021-11-06T05:25:45Z

I've been trying to upgrade a site to Gatsby v4 and discovered the issue also affects gatsby-remark-relative-images.

Plugin uses "main": "dist/index.js", in package.json and is currently breaking v4 with the same error.

Just confirming that I reproduced this bug on my site as well.

LekoArts · 2021-11-09T10:09:54Z

Please update to

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

fshowalter · 2021-12-04T19:41:25Z

@LekoArts possible this is hitting gatsby-remark-smartypants too? fshowalter/franksmovielog.com#551

lucantini · 2022-07-19T22:03:14Z

@LekoArts I still see this error with the following versions:

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

I don't use gatsby-remark-autolink-headers. Node version is set to v16.14.2.

gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 26, 2021

pieh self-assigned this Oct 26, 2021

pieh added topic: remark/mdx Related to Markdown, remark & MDX ecosystem type: bug An issue or pull request relating to a bug in Gatsby and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Oct 26, 2021

pedrolamas mentioned this issue Oct 26, 2021

Add support for Gatsby v4, change output config pedrolamas/gatsby-remark-acronyms#246

Merged

pragmaticpat added the gatsby 4 label Oct 26, 2021

akabekobeko mentioned this issue Oct 28, 2021

Gatsby v4 Support akabekobeko/npm-gatsby-remark-copy-relative-linked-files#34

Closed

j-e-clark mentioned this issue Nov 1, 2021

Cannot find module file index danielmahon/gatsby-remark-relative-images#59

Open

LekoArts mentioned this issue Nov 8, 2021

"gatsby-transformer-remark" threw an error while running the setFieldsOnGraphQLNodeType lifecycle: Cannot read property 'setParserPlugins' of undefined #33878

Closed

2 tasks

pieh mentioned this issue Nov 8, 2021

fix(gatsby): allow not defining entry for subplugins #33900

Merged

LekoArts closed this as completed in #33900 Nov 9, 2021

jpedroschmitz mentioned this issue Nov 12, 2021

chore(deps): update project dependencies jpedroschmitz/rocketdocs#113

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Subplugins loading doesn't respect `main` field in `package.json` #33677

Subplugins loading doesn't respect `main` field in `package.json` #33677

pieh commented Oct 26, 2021

akabekobeko commented Oct 28, 2021 •

edited

Loading

j-e-clark commented Nov 1, 2021

ehowey commented Nov 6, 2021

LekoArts commented Nov 9, 2021

fshowalter commented Dec 4, 2021 •

edited

Loading

lucantini commented Jul 19, 2022

Subplugins loading doesn't respect main field in package.json #33677

Subplugins loading doesn't respect main field in package.json #33677

Comments

pieh commented Oct 26, 2021

akabekobeko commented Oct 28, 2021 • edited Loading

j-e-clark commented Nov 1, 2021

ehowey commented Nov 6, 2021

LekoArts commented Nov 9, 2021

fshowalter commented Dec 4, 2021 • edited Loading

lucantini commented Jul 19, 2022

Subplugins loading doesn't respect `main` field in `package.json` #33677

Subplugins loading doesn't respect `main` field in `package.json` #33677

akabekobeko commented Oct 28, 2021 •

edited

Loading

fshowalter commented Dec 4, 2021 •

edited

Loading