Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

upgrade to node 12 #82

Merged
merged 2 commits into from
Jan 15, 2020
Merged

upgrade to node 12 #82

merged 2 commits into from
Jan 15, 2020

Conversation

prime-time
Copy link
Contributor

@prime-time prime-time commented Dec 6, 2019

This pull request was autogenerated

This pull request upgrades node to v12 which is the current long term supported version.

Node 12 runs on a newer version of the V8 engine which includes performance gains, better memory management, and access to the latest JavaScript syntax.

Here's the release blog post https://medium.com/@nodejs/introducing-node-js-12-76c41a1b3f3f.

Some of the improvements are highlighted below.

Node 12 improvements

Useful new JavaScript features

Better async stack traces

see more here https://v8.dev/blog/v8-release-72#async-stack-traces

async function foo(x) {
  await bar(x);
}

async function bar(x) {
  await x;
  throw new Error("Let's have a look...");
}

foo(1).catch(e => console.log(e.stack));

node 10

Error: Let's have a look...
    at bar (/Users/renatoprime/go/src/github.com/Clever/sd2/node12StackTraces.js:7:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:832:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

node 12

Error: Let's have a look...
    at bar (/Users/renatoprime/go/src/github.com/Clever/sd2/node12StackTraces.js:7:9)
    at async foo (/Users/renatoprime/go/src/github.com/Clever/sd2/node12StackTraces.js:2:3)

--The Node guild

@prime-time prime-time self-assigned this Dec 6, 2019
@prime-time prime-time merged commit 9009e00 into master Jan 15, 2020
@prime-time prime-time deleted the node-12 branch January 15, 2020 09:24
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.

3 participants