Hey @julien-f! 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
community that typically always has someone willing to help. You can sign-up here
for an invite.

Wouldnt node: "engines" be more explicit and readable? Although it's also worth discussing if engines could support also some format for browsers - and if yes then this should be a top-level option and not only for node.

engines is already a standard field in package.json, see the documentation.

Concerning the browsers, preset-env uses browserslist which does expose a pseudo-standard browserslist field (doc).

I know its a standard field, but as it is an object with "node" key and it could easily support browsers too - but i guess it could have been more useful for other things (i.e. when consuming packages with specified engines.browsers) and is not tightly related to your request

Yes, it could support browsers as well, but this probably an issue that should be created in the browserslist repo :)

For history/reference: babel/babel-preset-env#114

It should just read from engines by default, like it reads from browserslist by default. Zero configuration FTW!

That you have to set this up manually is my single biggest frustration with present-env. In .babelrc.js I require package.json and pull in engines.node.

It is shocking how many published packages don't follow best practice to define engines.node; making it the default way to configure preset-env could really help this situation.

Agreed, but this should be overridable (maybe with node: false).

Is this ticket still open?

@grantlouisherman yes

@xtuc I would like to take it if possible.

Is the code responsible for this located here?
https://github.com/babel/babel/blob/master/packages/babel-preset-env/src/targets-parser.js#L145

You can reference a previous PR for this over at the old repo: babel/babel-preset-env#114.

Keep in mind, there were some unresolved questions in that thread that we might want to nail down :)

Excuse my naivety on this issue(and the Babel project in general), but why cant the node field in targets just have a simple true or false value, and require that people set their node version in package.engines.node in their package.json?

In the package.json, you'd have to explicitly specify "current", ">=6" etc.

Is this issue still open? Can I claim it? :)

Is this still available to work on?

I believe so.

@existentialism do you confirm?

What would be really nice is to be able to specify the node targets in package.json, e.g. nodeTargets, and also make use of browserlist key in package.json as well. Right now if you specify a targets option in .babelrc and also have .browserlistrc file, the .browserlistrc file will not be read. In some cases such as using eslint with plugins like eslint-plugin-compat (to check for browser compatibility using caniuse database) - you always need to specify the same browserlist string... It's quite ugly.