-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Change default target to LTS #13
Comments
I'm OK with that but we'll need a trusted API to get the latest Node version. Ideally an npm package that contains Node.js versions or something so that there's no loading time during build. |
Isn't it just changing this line here from I do think we should manually set the target and update the LTS target versions ourselves, so every time the default target changes we can mark it as a breaking change. |
Now it's Node 18. |
I think having the default target to be reliant on
process.versions.node
creates a lot of inconsistency especially if you use a multitude of environments such as local and CI.To fit closer to the paradigm of zero-config, it might be better for the bundler to default to Node LTS instead for best practices.
I'm not sure if this should be considered a breaking change considering the existing setup already led to inconsistent bundles.
The text was updated successfully, but these errors were encountered: