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
Resolve .browserslistrc
as a project-wide file
#13028
Resolve .browserslistrc
as a project-wide file
#13028
Conversation
// TODO: browserslistConfig is currently resolved starting from the root | ||
// rather than from the config file. | ||
// eslint-disable-next-line jest/no-disabled-tests | ||
it.skip("loads nested .browserslistrc files if explicitly specified", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a separate bug, I found it while attempting to write a test. I'll fix it in a follow-up PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 35f8149:
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/44459/ |
5090cd4
to
35f8149
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok so treating .browserslistrc as babel.config.js file
Resolving
.browserslistrc
as file-relative config files was a decision took in the RFC and not something that I did accidentally, but:@babel/preset-env
works