JavaScript in 2022 - New, Coming and Proposed Features

Episode Summary

Executive Summary: The episode reviews major JavaScript and Node.js proposals/updates expected in 2022, focusing on making the ecosystem more ergonomic and interoperable. The hosts emphasize built-in fetch in Node, URL imports, JSON modules, import assertions, node:-prefixed built-ins, the pipeline operator, reversible split, module blocks, string.cooked, and BigInt math, framing them as quality-of-life improvements that reduce dependencies and bridge browser, Node, and standards-based APIs.

Main Topics: Fetch coming to Node.js: The hosts discuss fetch arriving as a global API in Node, initially under an experimental flag and likely backported to LTS releases, reducing the need for node-fetch or isomorphic fetch. URL imports in Node: They explain that Node is moving toward importing modules directly from HTTPS URLs, enabling dependency-free scripts while raising security and integrity concerns similar to hashed asset loading. JSON modules and import assertions: The episode covers native JSON imports using import assertions, a pattern that can also support other asset types like text and reduces reliance on bundlers for simple data loading. node: import scheme for built-ins: They highlight the node: prefix for built-in Node modules like path, fs, and crypto, which improves clarity, avoids collisions, and parallels future standards work in JavaScript itself. Pipeline operator and function composition: The hosts explain the pipeline operator as a way to 'hot potato' values through sequential functions, making nested transformations easier to read and potentially replacing temporary variables. Smaller language proposals and ergonomics: They briefly discuss reversible string split, JavaScript module blocks, string.cooked, and BigInt math as convenience-focused proposals that improve developer experience and fill gaps in the language.

Key Arguments: Built-in fetch in Node removes a common dependency and aligns Node with browser and Deno APIs, making it easier for developers to write portable code. URL imports can eliminate npm install for simple scripts, but require integrity/security mechanisms because remote code can change. JSON modules should be supported natively because many current JSON imports are handled by bundlers rather than the language/runtime itself. The node: prefix makes built-in imports immediately recognizable and reduces ambiguity with local files or npm packages of the same name. The pipeline operator improves readability by expressing data flow left-to-right instead of nesting function calls from the inside out. Reversible string split is useful because many developers from other languages expect split to return the remainder, not discard it. Module blocks may help with restrictions around importing code into environments like web workers and CSS Houdini, though the use case was not fully clear to the hosts. string.cooked is appealing as the inverse of string.raw and could simplify tagged template literal workflows. BigInt math proposals matter for developers handling very large numbers, extending the standard library for a specialized but real need.

Data Points: Node.js release trajectory: Node 16, 17, 18 - The hosts refer to even-numbered releases as long-term support and discuss fetch arriving in newer Node versions/backports. Monthly active users free tier: 100 - Magic Bell sponsorship offer includes a free 100 monthly active users tier. Discount duration: 12 months - Magic Bell coupon code syntax FM provides 10% off for the first 12 months. Sentry free period: 2 months - Sentry sponsorship offer includes two months free with coupon code tasty treat. BigInt math: Proposal status - A proposal exists to add math functions for BigInt values such as min and max.

Pivotal Quotes: "It's a web API, which is governed by the what WG? The whatWig." — Scott Tolinsky: Explaining that fetch belongs to web standards rather than JavaScript language core. "I always just call it hot potato, throw the data from one function to another." — Wes Bos: Describing the pipeline operator as a way to pass values through sequential transformations. "The idea there is that if there's ever, if there's ever overwrites in naming or collisions... this will sort of alleviate any of those potential edge case issues." — Wes Bos: Explaining why Node uses the node: prefix for built-in modules.

Implications: These proposals point to a more unified JavaScript ecosystem with fewer dependencies, clearer imports, and better language ergonomics. Listeners should expect gradual but meaningful improvements in portability, readability, and standards alignment across Node, browsers, and tooling.