JavaScript, TypeScript, runtimes and the surrounding toolchain.
Showing 1–3 of 3 dossiers
Node.js shipped v22.23.2, v24.18.1 and v26.5.1 to close a set of runtime vulnerabilities including an HTTP/2 use-after-free and a Permission Model path-matching bug that can over-grant filesystem access.
Bun 1.4 combines an implementation-language rewrite with a larger built-in standard library and a substantial Node-compatibility push. For teams already running Bun, the practical task is to validate native addons, runtime behavior and workload-specific performance rather than treating this as a drop-in minor upgrade.
The new tracing path gives Supabase requests a shared trace_id across browser or app spans and backend logs, with support for OpenTelemetry-compatible tooling. For JavaScript users, the practical detail is a required upgrade to supabase-js 2.112.0 or later because 2.106.0 through 2.111.x silently failed to propagate headers in bundled applications.
JavaScript sits in browsers, servers, build systems and an expanding range of runtimes. That reach creates genuine capability alongside a constant stream of packages, tooling resets and performance claims. The useful signal is the change that improves compatibility, security or the experience of shipping real software.
BTN follows language proposals, TypeScript, runtimes, package infrastructure and important tooling shifts. Coverage starts with primary specifications and release material, then asks what breaks, what becomes simpler and whether a new approach earns its migration cost. This is a place for durable JavaScript developments rather than every framework launch that happens to be popular for a week.
Browser and server JavaScript overlap, but they do not have identical constraints. BTN keeps that distinction clear while following shared standards, dependency security and the tools that move code between environments. A change earns attention when it makes a real application easier to ship, debug or keep compatible.