Skip to content

Conversation

@JamieMagee
Copy link
Contributor

Due to an update in the v8 runtime, Node.js Array.prototype.sort() is now stable (See here).

These changes allow for tests to pass on both Node.js 10 and 11.

Fixes #3445

Due to an update in the v8 runtime, Node.js Array.prototype.sort() is now stable (See [here](nodejs/node#22754 (comment))).

These changes allow for tests to pass on both Node.js 10 and 11.

Fixes #3445
@JamieMagee
Copy link
Contributor Author

@rarkins Is it worthwhile to update the engines in package.json. Something like ^10.13.0||^11? And add Node.js 11 to the .travis-ci.yml build matrix as well?

@rarkins
Copy link
Contributor

rarkins commented Apr 16, 2019

@JamieMagee that sounds like a good idea. Thanks for finding the solution

@rarkins rarkins merged commit 05a46dd into renovatebot:master Apr 16, 2019
@renovate-bot
Copy link
Collaborator

🎉 This PR is included in version 16.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@JamieMagee JamieMagee deleted the node-11 branch September 25, 2019 20:07
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Node.js 11

3 participants