r/javascript • u/jcready __proto__ • May 30 '17
Node 8.0.0 released
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md16
u/VertiGuo May 31 '17
Here's the blog post for the release: https://nodejs.org/en/blog/release/v8.0.0/
7
u/up_to_bot May 31 '17
As someone who hasnt touched node yet is this a big deal?
7
u/MildlySerious May 31 '17
The biggest deal I see in this is defaulting to npm 5, which brings a majority of the features yarn was introduced for.
Actual node devs might say the async stuff is a big deal, I personally can't comment on that.
Other than that it just seems like a proper major release, with some cleanups here and there, new deprecations, the usual stuff.
1
u/djslakor May 31 '17 edited May 31 '17
Yarn is still quite a bit faster. We don't see any reason to transition back to npm. In fact, @maybekatz who works on NPM5 just recently did a PR for yarn that made it even faster. :)
Async is a big deal, but it was in 7.x, too.
2
u/Akkuma May 31 '17
Yarn isn't that much faster based on benchmarks I've seen, https://github.com/JamieMason/npm-cache-benchmark
Based on that it is negligible and semver versioning of git dependencies in npm5 is way sweeter than a few less seconds.
1
u/maybekatz Jun 01 '17
it varies wildly. I've seen both yarn and npm5 shit the bed in major ways on random repos, and even random different people's computers.
FWIW it's kinda cool that both tools are at a point now that miscellaneous environment stuff has a big enough effect on performance that it changes the profiles of both tools.
0
u/djslakor May 31 '17
I've used it in production. Every day when I update our yarn.lock/package-lock.json, I see how long it takes. Not benchmarks.
52
u/norlin May 30 '17
and still no native import/export :(
31
u/VertiGuo May 30 '17
It's a hard problem to solve. See https://medium.com/the-node-js-collection/an-update-on-es6-modules-in-node-js-42c958b890c
5
u/norlin May 30 '17
Yeah, I know, but still there was a hope.
22
u/lachlanhunt May 30 '17
If you'd read that article before, you'd have seen the last paragraph that said:
At the current point in time, there are still a number of specification and implementation issues that need to happen on the ES6 and Virtual Machine side of things before Node.js can even begin working up a supportable implementation of ES6 modules. Work is in progress but it is going to take some time — We’re currently looking at around a year at least.
(Emphasis added)
3
1
u/Graftak9000 May 31 '17
It's my understanding the challenge comes from asynchronous loading, so why not start by transitioning to the export/import syntax, then at least some packages will be ES6 module compliant by the time support hits.
1
May 31 '17
I actually think that they are making the right move here -- import/export in ES6+ is fundamentally async. If they implement their own synchronous version, Node is now using parts of the standard JavaScript language in a non-standard way, which will become all but impossible to ever rectify.
The could extend 'require' to replicate the import/export syntax without using those keywords, but then they are going to be adding syntax into their framework when they know that it is only a temporary stop gap until they can properly implement import/export, which seems more than a little icky.
1
u/Akkuma May 31 '17
There are two projects working on this https://github.com/benjamn/reify & https://github.com/standard-things/esm
4
4
1
u/NizmoxAU May 30 '17
I'm not really convinced why it's needed in Node. But it should have been obvious it wasn't coming given it wasn't in v7.
23
u/norlin May 30 '17
It's almost available in browsers, so it's always better to keep things the same way both in browser and in node. And since it's native way in Javascript, it should be used instead of requires.
0
May 31 '17
[deleted]
5
May 31 '17
CJS is non-standard JavaScript. The
import/exportsyntax is the standard being adopted in browsers and should be adopted in Node as well.If we're not getting Node to at least adhere to JavaScript standards then what's the point?
0
u/thepeka May 31 '17
This idea is so painfully out of touch with reality.
1
u/FormerGameDev Jun 02 '17
I'd vote for a separate branch that ditches CJS and just uses ES6. I'd use it, at least in some things.
2
u/dvlsg May 31 '17
I mean, it's not needed, but being able to statically analyze modules sure would be nice.
4
u/pier25 May 31 '17
I just played around with async/await yesterday for the first time and it's glorious.
I thought it would be some black magic voodoo thing but it's actually super easy. Here is a nice presentation that explains how to use it.
3
u/MinicD May 30 '17
Is anyone having problem installing node v.8 on Ubuntu 16.04?
10
u/BenjiSponge May 30 '17
It's actually just "node 8" now (to avoid confusion with the v8 engine).
And, no. I use nvm and just upgraded with no issue.
48
1
2
u/djslakor May 31 '17
I recommend using nvm. It's much much easier to switch among versions. Super easy to setup, too. Just cut and paste their shell script from nvm's github page ... then nvm install node.
1
u/NoInkling May 30 '17
If you're using apt you probably need to add the repository for the new version.
1
1
u/calsosta May 31 '17
So we have 6, 7 and 8 all going at once? Is there any point to this?
0
May 31 '17
[deleted]
17
u/VertiGuo May 31 '17
And to add on to this, see https://github.com/nodejs/LTS
tl;dr: Odd numbered versions are experimental releases for those who want to stay on the bleeding edge. Even numbered versions are long term support releases that have extended maintenance windows. The overlap is presumably to give people time to transition over.
73
u/[deleted] May 30 '17
i was curious if they were going to do something like this