The Node.js Update - #Week 29 - 20 July, 2018

Below you can find RisingStack's collection of the most important Node.js news, updates & tutorials from this week:

Node.js 10.7.0 (Current) is out - update now!

  • console: The console.timeLog() method has been implemented.
  • deps:
    • Upgrade to libuv 1.22.0.
    • Upgrade to ICU 62.1 (Unicode 11, CLDR 33.1).
  • http: Added support for passing both timeout and agent options to http.request.
  • inspector: Expose the original console API in require('inspector').console.
  • napi: Added experimental support for functions dealing with bigint numbers.
  • process:
    • The process.hrtime.bigint() method has been implemented.
    • Added the --title command line argument to set the process title on startup.
  • trace_events: Added process_name metadata.
  • Added new collaborators: codebytere - Shelley Vohr

Download the latest Node.js version now!


Operationalizing Node.js for Server Side Rendering at Airbnb

As Airbnb builds more of its Frontend around Server Side Rendering, and they took a look at how to optimize server configurations to support it.

airbnb-nodejs-server-side-rendering

Server side rendering represents a different workload from the canonical, mostly I/O workload that Node.js excels at. Understanding the cause of anomalous behavior allowed us to address it with off the shelf components with which we had existing operational experience.


N-API: Next generation APIs for Node.js native addons available across all LTS release lines

You may have heard that Node.js has experimental support for N-API, a new API for native modules. Not anymore! N-API is now a stable and fully supported feature of Node.js as of version 10. It is also available as an experimental feature in Node.js 8 and 6.

nodejs-n-api

With N-API, native module developers can compile their module once per platform and architecture, and make it available for any version of Node.js that implements N-API. This holds true even for versions of Node.js that are built with a different VM, e.g. Node-ChakraCore.


npm enables two-factor authentication protection for packages

You can now beta-test two-factor authentication protection for individual packages in the npm Registry. This setting requires that every publication of a protected package be authorized by a one-time password. This requirement is enforced even if maintainers of that package haven’t required two-factor auth for publication themselves—they’ll still be prompted for a code for this package. If a maintainer hasn’t enabled two-factor auth at all, they’ll be unable to publish the package until they do.

npm-nodejs-two-factor-authentication

You can test this feature using the npm canary client, npmc. It's recommended to invoke the canary using npx: npx npmc. You can also install the canary build of npm directly by running npm install -g [email protected]


[EVENT] Designing Microservice Architectures with Node.js & Kubernetes

During the course of these two days, we will cover a high-level architectural overview of what is needed to design, develop and maintain an application built with microservices.

We will examine a microservices application developed adhering to current best practices, deploy it on Kubernetes and add the necessary infrastructural elements to make it resilient and self-healing.


[EVENT] Today is the last day to get early-bird tickets for JS Interactive!

Today is the last day to get early bird tickets for #JSInteractive. Save $349 USD by registering NOW: http://bit.ly/JSIEarlybird

The event takes place in Vancouver, Canada from October 10-12!


Previous Node.js Updates:

From the previous Weekly Node.js Update:

  • Postmortem for Malicious ESlint Packages Published on npm
  • Testing Node.js in 2018
  • Node.js REPL in Depth

& more...

We help you to stay up-to-date with Node.js on a daily basis too. Check out Node.js Daily!