-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
What is new in v6? #6264
Comments
That's not a complete listing. Apparently I forgot to update the notable changes in the changelog when I cut RC.2. Will fix that in RC.3. The big omission there, of course, is the v8 v5 update but there are a few others. |
Other semver-major changes I can think of offhand:
|
|
|
3.. best not to worry about it too much I'm not actually sure it is that noteworthy. It bring the subsystem architecture back to how it originally was, perhaps increasing some performance in some cases.
it wasn't even major; it's in v5. |
I need to finish my breaking changes doc, but it's pretty close to done. Doesn't overlap with this, but doing new features docs in similar ways may be helpful. |
Ah ok. Nevermind then. Perhaps we should also put together a more comprehensive summary for users upgrading from v4, since this is a new LTS release, rather than saying "read the v5 changelogs too?" |
@mscdex +1 ... just not in the changelog per se. I plan to go through and compile separate listings of all the semver-major and semver-minor updates that have been made since v4.2. It's going to take a bit of time to do, however. I'm planning to work on it later this week. |
When to expect final release? |
@bricss AFAIK we're shooting for the 26th |
Yep, the 26th. RC.3 should hit a bit later on this afternoon. Going to start working on it around 3:30 |
Here is the current list of notable changes for v6 in RC.3 ... please take some time to hammer away at this and let me know what's missing, what shouldn't be there, or any other changes I should note. See jasnell@59bc4db for the full commit log showing the semver-major changes since v5.0.0 and the minor/patch changes since v5.10.1.
|
@jasnell How (if at all) is the newer v8 release that fixes that harmony regexp command-line flag going to work? Is the plan to merge it before the final release or for an rc4 or something else? |
Typo, should it be the 5.0.71.32 according to the link? Will it be 5.0.71.33 in the release? |
@vsemozhetbyt @mscdex ... hoping that lands. Haven't seen a PR for it yet tho. |
The V8 upgrade to 5.0 means that Node 6.0 will be at 93% of ES6 features supported (up from 56% for Node 5.x, and 50% for Node 4.x). |
Might be worth mentioning #3594, both for the improved performance, and the API change (cache parameter removed). |
@ofrobots That's not only 93% of all es2015 (aka es6) features, but also 50% of all es2016 (aka es7) features. Namely, |
@jasnell That list is just the striped down breaking changed though, right? Or does that also include features from semver-minors in v5? |
Just the breaking changes. Not the minors
|
Apparently Node v6.0.0 does not support the ES2015 module import and export syntax yet. Is this correct? (Can't find reference on this at http://node.green.) If so, is ES2015 module support something in the road map? |
@aidanbon Some of the details have been hashed out, see nodejs/node-eps#3 (warning: big thread), but there's also quite a bit of work that needs to be done on the V8 side. v7 is the soonest you should expect it but I wouldn't be surprised if it slips until v8. |
(Or it may not land at all.) |
Likely no reason to keep this issue open any longer. |
Since v6 release is imminent we need to get together a good list of high level things we can say are in the new release.
The text was updated successfully, but these errors were encountered: