You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two types of configuration files: babel.config.js and .babelrc.js (docs).
.babelrc files are very expensive to load, because we must check if they are present in the file's folder or in any parent folder. They are also rarely used, because for 99% of use cases babel.config.js is enough. To save on I/O cost, we should only load them if the babelrc option is explicitly set to true.
However, this change has a disadvantage: some people like to keep their config in package.json, and we threat it as if it was a .babelrc file. Maybe we should add a rootConfig: true option in package.json#babel, to make it behave like a babel.config.json?
The text was updated successfully, but these errors were encountered:
We have two types of configuration files:
babel.config.js
and.babelrc.js
(docs)..babelrc
files are very expensive to load, because we must check if they are present in the file's folder or in any parent folder. They are also rarely used, because for 99% of use casesbabel.config.js
is enough. To save on I/O cost, we should only load them if thebabelrc
option is explicitly set to true.However, this change has a disadvantage: some people like to keep their config in
package.json
, and we threat it as if it was a.babelrc
file. Maybe we should add arootConfig: true
option inpackage.json#babel
, to make it behave like ababel.config.json
?The text was updated successfully, but these errors were encountered: