Pnpm v9.0.0; Biome v1.7; ESLint v9.1.0; Node.js collaboration summit; Intl.Segmenter; tree shaking;

• Lockfile v9
• Corepack compatiblity
• MacOS uses same directory for state files as Linux
• When installing git-hosted dependencies, only pick the files that would be packed with the package
• Install subdirectories of Git repositories
• Support for PowerShell completions

• Intl is now recognized as a built-in global unless languageOptions.ecmaVersion is set to 3 or 5.
• The no-constant-condition rule no longer reports while (true) loops as problems by default.
• A configuration that contains a non-global ignores pattern list will no longer cause incorrect results when the --no-ignore CLI flag is used, or when the ESLint constructor option ignore is set to false.

“About twice per year, Node.js contributors and community members get together in an unconference called the Node.js collaboration summit. At the summit, we share knowledge about the project and the ecosystem, brainstorm solutions to technical and non-technical issues, make progress in decision-making discussions, and push forward new initiatives.”

Topics that were discussed:

• HTTP, web server frameworks and clients
• New features for the built-in CLI
• Version management of package managers and the Node.js binary
• Better asynchronous scheduling and memory management
• Release and CITGM
• Content curation, user survey and funding
• ECMASCript Modules and interoperability
• Participation in standards: TC39, WinterCG and security

Intl.Segmenter splits text into parts (graphemes, words, sentences) and supports many human languages.

“This web feature is now available in all three major browser engines, and becomes Baseline Newly Available as of April 16, 2024.”

Context:

• “Baseline identifies web platform features that work across browsers.”
• “Baseline features are described as either newly available in current stable browsers or widely available with continuous support over time.”

• Signal graphs, in most implementations, consist of Root State, Derived State, and Effects
• Sometimes, Effects are used to update root state with the results of async processes
• A common anti-pattern is to manage multiple pieces of root state with a singfle effect, or to use multiple effects to manage a single shared piece of root state, creating difficult to debug ownership and timing issues. We can label this anti-pattern as “disjointed implicit reactivity”.
• Relays isolate and co-locate these effects with the root state they manage, preventing these issues by ensuring that there is one (and only one) place that the state can be managed and updated from.