Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
ECMAScript 2025 finished the standards track with language features such as RegExp.escape, iterator helpers, and JSON module import attributes that engines implement on their own cadence.
Monitor engine release notes (V8, SpiderMonkey, JavaScriptCore) for shipping status rather than assuming immediate runtime availability.
MDN remains the day-to-day reference for built-ins like Set iteration helpers once engines ship them.
Cross-link to ECMA-262 when filing browser bugs that claim spec violations.
Because Node embeds V8, language features ship with Node upgrades—read the Node 22/24 release blogs for Float16Array and related V8 highlights.
Align TypeScript target with the actual Node runtime in production.
JavaScript evolves through staged proposals; understanding stages prevents teams from relying on syntax that may still change.
Use Babel or equivalent only with explicit policy for stage-3 features.
OWASP and MDN both discuss object graph hazards that remain relevant as new builtins land.
Static analysis rules should be re-tuned when language additions introduce new reflection surfaces.
After verifying support tables for each browser tier you support; the spec being final does not imply universal shipping.
Use Baseline data and manual tests on constrained devices.
Iterator helpers process lazily compared with array intermediates, but you still need backpressure when bridging to I/O; the spec defines semantics, not resource limits.
Profile memory when composing helpers with async iterators.
Module goals, resolution, and global builtins differ; Node’s CommonJS vs ESM semantics are not identical to browser module graphs.
Consult Node’s module documentation alongside ECMA-262 module grammar.
The finalized ECMAScript 2025 materials include JSON modules with import attributes; the HTML side covers how browsers fetch module graphs.
Link both when writing security reviews of dynamic imports.
Follow meeting notes in the tc39/notes repository and cross-reference proposal repos linked from the agenda.
Record decisions in your internal ADR log with proposal-stage snapshots.