-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Breaking change in v3.3.0: Node < 8 is not supported anymore by core-js-compat #669
Comments
Previous versions of this package were not compatible with Node 8-, moreover, with Node 8.3-, since here was used object spread syntax. Node 6 was available to work only in some cases like loading JSON data. Ok, I'll remove this field. |
Thanks! |
This was referenced Oct 24, 2019
This was referenced Dec 4, 2019
zloirock
referenced
this issue
in npm/node-semver
Dec 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi 👋
57f497d introduced the
engines.node
option incore-js-compat
's package.json.That package already works in node 6, since it uses only these "new" es features, which are supported in node 6
for...of
...
spread in function callsMap
/Set
(iterator closing is not supported)While that metadata-only change might seem innocuous, it causes
yarn
to fail when installing it:Would it possible to revert that change and:
engines
a node version which wasn't supported for real (e.g.>= 6.4.0
, according to https://node.green/)?
The text was updated successfully, but these errors were encountered: