Below you can find RisingStack‘s collection of the most important Node.js news, updates, projects & tutorials from this week:
One of the most significant drawbacks when switching contexts to Node is the lack of the Chrome Developer Tools. Luckily, there are options for enabling them, and they’ve gotten much more stable and usable in recent times.
A Node.js process started without inspect can also be instructed to start listening for debugging messages by signaling it with SIGUSR1 (on Linux and OS X).
One of the most significant issues for developers is to figure out why their apps are slow. So far, there weren’t too many tools that deal with performance issues. Luckily, NearForm came up with a solution: Node Clinic – a performance toolkit for Node.js.
Simplifying tooling setup can save a lot of time and energy when creating apps. Wrapping tools like Babel, ESLint, or Prettier provides a great solution for this issue; go with tools that come pre-configured and don’t spend unnecessary time on your setup.
Would you like to know more about the Node.js Fundamentals, Microservices, Kubernetes, Angular, or React? We have good news for you!
Making sure that your npm package works as expected after publishing on npm can be a nightmare.
In this post, we’re going to explain how to create a public npm registry dedicated for testing your npm package on both your machines and servers before releasing it officially.
Switching to HTTPS is crucial to ensure safety. Good news is that you can do it for free with ‘Let’s Encrypt and NGINX’. It should only take about 30 minutes… This article guides you through the process step-by-step.
Previously Node.js Updates:
In the previous Weekly Node.js Update, we collected great articles, like
- Learn Node.js — Directory of top articles from last year (v.2018);
- A crash course on TypeScript with Node.js;
- How does Node load built-in modules;
- Migrating your Node.js REST API to Serverless;