You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is hard to replicate that in a browserslist query:
Node 12 - 13 and Node < 13, Node >= 13.7.0
One gotcha is that browserslist has a different behavior than the npm ecosystem when considering a major number on it's own: Node 12 in browserslist will select only the newest v12 version, but 12 in package.jsonengines or dependencies selects every version in that major.
It would be nice if browserslist used the semver semantics, allowing the same semver version and range strings that we're used to using in package.json, e.g.
Node ^12.0.0 || >= 13.7.0
Or this, which is the same:
Node 12 || >= 13.7.0
The text was updated successfully, but these errors were encountered:
If you have this in your
package.json
:It is hard to replicate that in a browserslist query:
One gotcha is that browserslist has a different behavior than the npm ecosystem when considering a major number on it's own:
Node 12
in browserslist will select only the newest v12 version, but12
inpackage.json
engines
ordependencies
selects every version in that major.It would be nice if browserslist used the
semver
semantics, allowing the same semver version and range strings that we're used to using inpackage.json
, e.g.Or this, which is the same:
The text was updated successfully, but these errors were encountered: