fix(gatsby): Support ESM-only gatsby-remark-*
plugins
#37440
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When writing a local plugin (inside
plugins
)/using external plugin forgatsby-transformer-remark
orremarkPlugins
array ofgatsby-plugin-mdx
, this remark plugin didn't support being written in ESM.This was due to no correct handling in the
subPlugins
validation. In addition to theresolve
andoptions
key of the plugin that a user might write in their gatsby-config, we're also addingmodule
andmodulePath
to the object in the validation step. Previously, themodule
key was usingrequire()
. Now it usesawait import
.Documentation
One expects it already works so no change needed.
Related Issues
[ch59936]