Please add example on using .babelrc settings (by using cacheIdentifier?)

cacheIdentifier: Default is a string composed by the babel-core’s version, the babel-loader’s version, the contents of .babelrc file if it exists and the value of the environment variable BABEL_ENV with a fallback to the NODE_ENV environment variable. This can be set to a custom value to force cache busting if the identifier changes.

Sounds like I could use cacheIdentifier to use my babel settings defined in .babelrc but not sure how to use it. Please advice 😃

[MrSaints]

I believe if the .babelrc is in a different place you can specify its location using the babelrc option on the query config property.

Tried that, you end up with:

Module build failed: Error: .babelrc must be a boolean, or undefined

It does not look like you can set a fixed location.

You can set a base .babelrc using:

options: {
    extends: path.resolve(__dirname, ".babelrc.js"),
}

Tested on Babel 8. Perfect if you are importing from outside the current working directory.

[Slapbox]

@loganfsmyth I’ve not been able to get babel-loader@8.0.5 to recognize my .babelrc files in my app folder. I run webpack from my project root and I have a project setup like this:

ProjectRoot/
  babel.config.js
  app/desktop/.babelrc
  webpack_configs/.babelrc

~~The full project has more folders and more .babelrc files, which is why I’m using babel.config.js. ~~

From what I understand Babel-Loader should pick up the .babelrc in the app/desktop folder from what I can tell, but instead I get errors resulting from none of the plugins/presets being defined. I’ve been defining these in parallel in my webpack config, but I’m trying to dry things up.

I didn’t want to make a new issue for something that’s already been discussed to death, but I also can’t find a solution among any of the discussions. If you have any ideas I’d really appreciate it!

Looks like my problem is probably with on of my .babelrc files