This looks like an interesting framework for everything error-related. The core handles the usual tasks (wrapping errors, creating classes, etc.) and plugins offer more advanced use cases (serialization, CLI errors, logging, etc.).

For all your object wrangling needs:

• ⛏️ Dot-delimited paths: foo.bar.0.baz
• ⭐ Wildcards: foo.*, **.bar
• 🗺️ Regexps: foo./ba?/
• 🏜️ Slices: foo.0:2
• 🚂 Unions: foo bar baz

This is a map of known process signals with some information about each signal. Unlike os.constants.signals this includes:

• human-friendly descriptions
• default actions, including whether they can be prevented
• whether the signal is supported by the current OS

Handy!

nve differentiates itself from nvm run because it:

• can be run programmatically
• is 10 times faster
• does not need a separate installation step for each Node version
• works on Windows
• does not require Bash
• is installed as a Node module

Worth noting: this is not a full-on replacement for nvm or any other version manager. It only executes a single command with the specified Node version. But sometimes, that’s all you need. 😄

Why is writing portable Node code so important?

According to the 2018 Node.js user survey (using the raw data), 24% of Node.js developers use Windows locally and 41% use Mac. In production 85% use Linux and 1% use BSD.