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

@babel/preset-env doesn't respect browserslist config files relative to transpiled files #9429

jaydenseric opened this Issue Jan 30, 2019 · 1 comment


None yet
2 participants
Copy link

jaydenseric commented Jan 30, 2019

Bug Report

Browserslist will check config in every directory in path. So, if tool process app/styles/main.css, you can put config to root, app/ or app/styles.

Current Behavior

@babel/preset-env doesn't respect browserslist config files relative to transpiled files.

Input Code

With this directory structure:

├── .browserslistrc
├── babel.config.js
└── src/
    ├── index.js
    └── client/
    │   ├── .browserslistrc
    │   └── index.js
    └── server/
        ├── .browserslistrc
        └── index.js

Expected behavior/code

With different browserslist config in each of the 3 .browserslistrc files, you would expect each of the 3 index.js files would have transpiled accordingly.

In reality, only the top level .browserslistrc file is applied to all of the transpiled files.


  • Babel version(s): @babel/preset-env@7.3.1
  • Node/npm version: Node.js v10.15.0 / npm v6.7.0
  • OS: macOS 10.14.2
  • Monorepo: No.
  • How you are using Babel: cli

Additional context

A strong use case would be transpiling server and client files differently within the same package.


This comment has been minimized.

Copy link

babel-bot commented Jan 30, 2019

Hey @jaydenseric! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
that typically always has someone willing to help. You can sign-up here
for an invite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment