Below you can find RisingStack‘s collection of the most important Node.js updates, projects & tutorials from this week:
- expose ECDH class
- http2 is now exposed by default without the need for a flag
- a new environment variable NODE_NO_HTTP2 has been added to allow userland http2 to be required
- support has been added for generic
- resolve and instantiate loader pipeline hooks have been added to the ESM lifecycle
- CVE-2017-14919 – In zlib v1.2.9, a change was made that causes an error to be raised when a raw deflate stream is initialized with windowBits set to 8. On some versions this crashes Node and you cannot recover from it, while on some versions it throws an exception. Node.js will now gracefully set windowBits to 9 replicating the legacy behavior to avoid a DOS vector.
A Node v8.8.1 fix was released on 26, October to fix timeout with null handle issue.
Keynote by @fhinkel tells everyone that V8 policy now is that no V8 commit can land if it breaks Node.js. ?
— Rich Trott (@trott) October 4, 2017
Have you just built an API with Node.js? If you’d really like to make a progress as a developer, you’ll have to start testing your APIs.
In this tutorial, you will learn how to write a Node.js API test. Dive in!
Node.js client library is supported by Google to assess Google APIs.
This library on Github is still in maintenance mode, as they are still working on some bugs and adding new features to meet the requirements of or accessing Google APIs. Code on!
This week, V8 version 6.3 has been announced, which is in beta until its release in coordination with Chrome 63 Stable in several weeks. V8 v6.3 is filled with all sorts of developer-facing goodies, such as improved speed, memory consumption, and debugging, as well as new ECMAScript language features.
By introducing multithreading to Node.js, the Napa.js runtime can more easily handle computation-intensive tasks.
How to do it? Check it out in this tutorial. You will create a lambda CRUD microservice which saved data in a DB.
Ryan Dahl, the creator of Node.js said the following while he was talking about Node’s concurrency model:
[…] I think Node is not the best system to build a massive server web. I would use Go for that. And honestly, that’s the reason why I left Node. It was the realization that: oh, actually, this is not the best server-side system ever.
What does this mean for the Node.js community? Is this the end of the Node-era?
By eliminating the language barrier, we hope that a lot of new developers can learn about the fantastic possibilities that Node.js provides.
Check it out!
When you develop an API, most of the times you’ll need part or all of its endpoints to require authentication. How to do that using Node.js?
A combination of passport.js with JWT and bcrypt is one of the best ways to implement it. Time to go stateless!
Previously in the Node.js Weekly Update