Node v8.5.0

#1

Post by bpierre » Wed, Sep 13, 2017, 12:40 AM UTC

Re: Node v8.5.0

#2

Post by pitaj » Wed, Sep 13, 2017, 1:22 AM UTC

> add fs.copyFile and fs.copyFileSync which allows for more efficient copying of files.

FINALLY. I don;t know how long we could have come with this still being a thing you need a module for, or you have to code yourself.

Hopefully we get `fs.mkdirp` and `fs.remrf` somewhere down the line.

> Add support for ESM. This is currently behind the `--experimental-modules` flag and requires the `.mjs` extension.

I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here.

Re: Node v8.5.0

#3

Post by maxpert » Wed, Sep 13, 2017, 1:33 AM UTC

Everyone busy with iPhone X bad day for such important post

Re: Node v8.5.0

#4

Post by ZenoArrow » Wed, Sep 13, 2017, 1:50 AM UTC

maxpert wrote: post #3

Everyone busy with iPhone X bad day for such important post

I think you could find plenty of people who couldn't care less about the iPhone X (you're speaking with one of them). I took one quick look, saw nothing of major interest, and moved on with my day.

Moving back to the linked story, are there any long running issues with Node that are still not yet addressed? Are nearly all common issues resolved?

Re: Node v8.5.0

#5

Post by argentenergy » Wed, Sep 13, 2017, 1:56 AM UTC

Does enable async stack traces mean useful stack traces?

Node has been a frustrating language to switch to from C# from the perspective of stack traces. It seems in node they devolve into relative meaninglessness beyond the first line or two. I have fond memories of juicy stack traces like homing beacons.

I'm secretly hoping somebody will jump in to tell me I'm just reading them wrong or something...

Re: Node v8.5.0

#6

Post by avaer » Wed, Sep 13, 2017, 2:00 AM UTC

ZenoArrow wrote: post #4

maxpert wrote: post #3

Everyone busy with iPhone X bad day for such important post

I think you could find plenty of people who couldn't care less about the iPhone X (you're speaking with one of them). I took one quick look, saw nothing of major interest, and moved on with my day. Moving back to the linked story, are there any long running issues with Node that are still not yet addressed? Are nearly all common issues resolved?

Which long running issues?

All common issues are quickly resolved, almost by definition, in a long-running successful project like node. Lots of people depend on that being the case.

It's just not always resolved in core (which is why npm/yarn/webpack and a hundred other awesome derived works exist).

Re: Node v8.5.0

#7

Post by [deleted] » Wed, Sep 13, 2017, 2:12 AM UTC

argentenergy wrote: post #5

Does enable async stack traces mean useful stack traces? Node has been a frustrating language to switch to from C# from the perspective of stack traces. It seems in node they devolve into relative meaninglessness beyond the first line or two. I have fond memories of juicy stack traces like homing beacons. I'm secretly hoping somebody will jump in to tell me I'm just reading them wrong or something...

[deleted]

Re: Node v8.5.0

#8

Post by bdcravens » Wed, Sep 13, 2017, 2:15 AM UTC

maxpert wrote: post #3

Everyone busy with iPhone X bad day for such important post

Not sure what that even means. I watched the keynote, decided I'll probably buy it when it comes out, had a few minutes of banter here on HN, and that was it. Then back to real life for the other 22.5 hours of today. :-)

Re: Node v8.5.0

#9

Post by jadbox » Wed, Sep 13, 2017, 2:17 AM UTC

argentenergy wrote: post #5

Does enable async stack traces mean useful stack traces? Node has been a frustrating language to switch to from C# from the perspective of stack traces. It seems in node they devolve into relative meaninglessness beyond the first line or two. I have fond memories of juicy stack traces like homing beacons. I'm secretly hoping somebody will jump in to tell me I'm just reading them wrong or something...

Yes, this update will make async stack traces appear within its called context... allows for much better debugging. https://medium.com/the-node-js-collection/node-js-8-big-impr...

Re: Node v8.5.0

#10

Post by sintaxi » Wed, Sep 13, 2017, 3:11 AM UTC

pitaj wrote: post #2

> add fs.copyFile and fs.copyFileSync which allows for more efficient copying of files. FINALLY. I don;t know how long we could have come with this still being a thing you need a module for, or you have to code yourself. Hopefully we get `fs.mkdirp` and `fs.remrf` somewhere down the line. > Add support for ESM. This is currently behind the `--experimental-modules` flag and requires the `.mjs` extension. I don't like…

I like .mjs because this is a good example of exactly what file extensions are meant for.