rewrite gatsby-config & gatsby-node with node 11's experimental ECMAScript modules

Has anyone tried replacing module.exports/require() in gatsby-config.js and/or gatsby-node.js with the experimental import/export syntax introduced in node v11.10.1? I’m interested in advice on how to make the transition, whether or not I should wait and if there are any limitations.

[harrysolovay]

Okay, I’ll take a shot at it.

From what I can tell. Here are the changes that need to take place:

1. Creating a helper package that differentiates between ESMs & CJS:

const interopRequire = path => {
  const required = require(path)
  return required.__esModule ? required.default : required
}

1. In packages/Gatsby/src/internal-plugins/internal-data-bridge/gatsby-node, add the require highjack:

require = require(‘esm’)(module)

…Along with––at line 121––swapping out the require with interopRequire

One question: where are the other user-defined config resources being required? I searched for a while but couldn’t find exactly where it happens. If anyone could let me know, that would be so so nice. Thanks 💯

[harrysolovay]

@wardpeet I like that solution––esm is a great project. Could you or someone who has familiarity with the Gatsby codebase speak to whether the current caching would play nice with esm’s? If so, supporting ESModules would be as easy as adding the require highjack. Would love to be able to use this syntax.