Doesn't work if config is in "babel.config.js" file · kentcdodds/babel-plugin-codegen#18

(4 comments) (4 reactions) (0 assignees)TypeScript (27 forks)github user discovery

help wantedneeds investigation

Repository metrics

Plugin doesn't work if your Babel config is in babel.config.js, but all works fine if it is in .babelrc

babel.config.js

module.exports = function() {
  return {
    presets: ['babel-preset-expo'],
    plugins: ['codegen'],
  }
}

.babelrc

{
  "presets": ["babel-preset-expo"],
  "plugins": [
    "codegen"
  ]
}

What you did:

// @codegen

module.exports = '
  module.exports = []
'

What happened:

When I use babel.config.js, I get export from module as string "module.exports = []", like there is no top comment "// @codegen".

When I use .babelrc, I get empty array as export from module, as it should be.

Reproduction repository:

Latest Expo has babel config in babel.config.js, and I don't want to change it as it is the standard for all future releases.

Research direction: Investigate why the plugin fails when Babel config is in babel.config.js vs .babelrc. Check if the plugin uses relative paths or expects a file based config. Look into Babel's config resolution order and plugin loading behavior. Compare with known issues in other babel plugins regarding config file types.
Tech stack: javascriptnodejs
Domain: toolingbuild system
Issue type: Bug
Difficulty: 2
Estimated time: 1-3 hours
Activity status: Active
Clarity: Clear
Prerequisites: JavaScriptBabel configuration
Newbie friendliness: 65