-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
@vitejs/plugin-legacy does not use browserslistrc #2476
Comments
I can confirm that explicitly changing BTW what's up with PR #2627 |
@maxbublik I don't know why the PR was closed, this should be fixed. PR welcomed, someone could start from that closed PR and send a new one against the latest version |
browserslist is not working because plugin-legacy uses Switching to Handling browserslist on plugin-legacy or bundling babel on our side might increase maintenance burden. |
@sapphi-red By my test, it doesn't add additional dependency and increase bundle sizes, please see comparison results:
and it will not result in break change, because |
@KAROTT7 I was not talking about neither the dependency size nor the bundle size. I was talking about the number of dependencies (including transitive ones). The number of dependencies affects the install time. Anyway, in the last meeting, we decided to switch to |
Since |
…11318) Co-authored-by: 翠 / green <[email protected]> fixes #2476
…itejs#11318) Co-authored-by: 翠 / green <[email protected]> fixes vitejs#2476
Describe the bug
@vitejs/plugin-legacy
does not use browserlist config files. When thetargets
option is not specified, it is defaulted todefaults
, which means@babel/present-env
will use that target rather than.browserslistrc
.Reproduction
System Info
vite
version: 2.0.5Logs (Optional if provided reproduction)
With no targets option
With targets set to same value as in my .browserslistrc (>0.2%, not dead, not op_mini all)
The text was updated successfully, but these errors were encountered: