Environment "browser" and version "latest"

[AlicanC]

It would be nice if we had a "browser" environment which would cover all browsers and a "latest" version to target the latest version of an environment.

Examples:

{ browser: 'latest' }
// =>
{ chrome: 'latest', edge: 'latest', firefox: 'latest', safari: 'latest' }
// =>
{ chrome: 123, edge: 123, firefox: 123, safari: 123 }

[hzoo]

There's #19 which I believe covers this?

[AlicanC]

Not really. #19 just adds a special field (browsers) that uses browserslist. What I am suggesting is a solution for all fields (browsers, chrome, node, etc.).

[hzoo]

In a previous issue we asked if browser list would also add in node as well. I'm not sure you actually want latest for everything on the compat-table

[yavorsky]

I think, we can extend #19 according to this needs. Just parse implicit fields using browserslist if type of the field is a string, for ex.

[AlicanC]

I'm not sure you actually want latest for everything on the compat-table

You might not, but when you have it for browsers and not for Node.js the configuration becomes weird:

{
  "browsers": ["latest 2 versions"], OK
  "ie": "latest 3 versions", OK
  "node": "latest 2 versions" Error?
}

Type of the configuration looks like this:

type VersionNumber = number;
type BrowserslistQuery = string;

type Configuration = {
  browsers: Array<BrowserslistQuery>,
  edge: VersionNumber | BrowserslistQuery,
  chrome: VersionNumber | BrowserslistQuery,
  ...,
  node: VersionNumber,
};

This is very inconsistent.

[hzoo]

I was saying before Node could be added in the other pr to browserlist - babel/babel#3476 (comment)

[chicoxyzzy]

browserlist's issue to track browserslist/browserslist#75

[amilajack]

#19 was merged. Should this be closed?