Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to latest babel version and fix babelrc behaviour #583

Merged
merged 2 commits into from
Feb 25, 2018
Merged

Conversation

danez
Copy link
Member

@danez danez commented Feb 25, 2018

This removes the custom behaviour in babel-loader of the option
babelrc. It now cannot be a string anymore and should be boolean and instead
extends should be used.

BREAKING CHANGE: Option babelrc needs to be boolean now. String values are not allowed anymore. Use extends option to specify a specific config file. A warning will be triggered when setting babelrc to a string.

This removes the custom behaviour in babel-loader of the option
`babelrc`. It now cannot be a string anymore and should be boolean and instead
extends should be used.

BREAKING CHANGE: Option `babelrc` needs to be boolean now. String values are not allowed anymore. Use `extends` option to specify a specific config file. A warning will be triggered when setting babelrc to a string.
@danez
Copy link
Member Author

danez commented Feb 25, 2018

@loganfsmyth It would be nice if babel-core could somehow expose which config files are used for a specific source file. That way we wouldn't have to do the resolve of the babelrc files in the loader.

@@ -288,7 +300,8 @@ test.cb("should allow to specify the .babelrc file", t => {
exclude: /node_modules/,
query: {
cacheDirectory: t.context.cacheDirectory,
babelrc: path.join(__dirname, "fixtures/babelrc"),
extends: path.join(__dirname, "fixtures/babelrc"),
babelrc: false,
Copy link
Member Author

@danez danez Feb 25, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the breaking change basically, I couldn't figure out why we used a string value for babelrc in the first place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant