What is new in v6?

[mikeal]

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.

[jasnell]

See: https://github.com/jasnell/node/blob/v6-rc1/CHANGELOG.md

[jasnell]

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.

[mscdex]

Other semver-major changes I can think of offhand:

1. v8 5.0
2. Faster module loading
3. Timers refactor
4. 50% more cowbell

[mikeal]

1. what of note is in V8 5.0 compared to prior releases?
2. how much faster is module loading?
3. what does the timers refactor actually do?

[jasnell]

1. No API changes, new ES language features, perf improvements
2. https://benchmarking.nodejs.org/charts/require_new.png
3. @Fishrock123

[Fishrock123]

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.

Other semver-major changes I can think of offhand:

• Timers refactor

it wasn't even major; it's in v5.

[Fishrock123]

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.

[mscdex]

it wasn't even major; it's in v5.

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?"

[jasnell]

@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.

[bricss]

When to expect final release?

[mscdex]

@bricss AFAIK we're shooting for the 26th

[jasnell]

Yep, the 26th. RC.3 should hit a bit later on this afternoon. Going to start working on it around 3:30

[jasnell]

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.

• Buffer
  • New Buffer constructors have been added
    #4682
  • Previously deprecated Buffer APIs are removed
    #5048,
    #4594
  • Improved error handling #4514
• Cluster
  • Worker emitted as first argument in 'message' event
    #5361.
• Crypto
  • Improved error handling #3100,
    #5611
  • Simplified Certificate class bindings
    #5382
  • Improved control over FIPS mode
    #5181
  • pbkdf2 digest overloading is deprecated
    #4047
• Dependencies
  • Reintroduce shared c-ares build support
    #5775.
  • V8 updated to 5.0.71.31 #6111.
• DNS
  • Add resolvePtr API to query plain DNS PTR records
    #4921.
• Domains
  • Clear stack when no error handler
    #4659.
• File System
  • FS apis can now accept and return paths as Buffers
    #5616.
  • Error handling and type checking improvements
    #5616,
    #5590,
    #4518,
    #3917.
  • fs.read's string interface is deprecated
    #4525
• HTTP
  • 'clientError' can now be used to return custom errors from an
    HTTP server #4557.
• Modules
  • Current directory is now prioritized for local lookups
    #5689
• Net
  • DNS hints no longer implicitly set
    #6021.
  • Improved error handling and type checking
    #5981,
    #5733,
    #2904
• Path
  • Improved type checking #5348.
• Process
  • Introduce process warnings API
    #4782.
  • Throw exception when non-function passed to nextTick
    #3860.
• Readline
  • Emit key info unconditionally
    #6024
• REPL
  • Assignment to _ will emit a warning.
    #5535
• Timers
  • Fail early when callback is not a function
    #4362
• TLS
  • Rename 'clientError' to 'tlsClientError'
    #4557
  • SHA1 used for sessionIdContext
    #3866
• TTY
  • Previously deprecated setRawMode wrapper is removed
    #2528.
• Util
  • Changes to Error object formatting
    #4582.
• Windows
  • Windows XP and Vista are no longer supported
    #5167,
    #5167.

[mscdex]

@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?

[vsemozhetbyt]

V8 updated to 5.0.71.31

Typo, should it be the 5.0.71.32 according to the link?

Will it be 5.0.71.33 in the release?

[jasnell]

@vsemozhetbyt @mscdex ... hoping that lands. Haven't seen a PR for it yet tho.

[mscdex]

@jasnell #6290

[ofrobots]

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).

[mscdex]

@ofrobots This shows 96%.

EDIT: Ah, I think that may be because node.green counts compatibility even if it's behind the es-staging flag.

[jhamhader]

Might be worth mentioning #3594, both for the improved performance, and the API change (cache parameter removed).

[ChALkeR]

@ofrobots That's not only 93% of all es2015 (aka es6) features, but also 50% of all es2016 (aka es7) features. Namely, Array.prototype.includes. 😉

[Fishrock123]

@jasnell That list is just the striped down breaking changed though, right?

Or does that also include features from semver-minors in v5?

[jasnell]

Just the breaking changes. Not the minors
On Apr 26, 2016 7:16 AM, "Jeremiah Senkpiel" notifications@github.com
wrote:

@jasnell https://github.com/jasnell That list is just the striped down
breaking changed though, right?

Or does that also include features from semver-minors in v5?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6264 (comment)

[aidanbon]

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?

[bnoordhuis]

@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.

[Fishrock123]

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.)

[jasnell]

Likely no reason to keep this issue open any longer.