Node.js 24.20.0 'Krypton' LTS ships several SEMVER-MINOR additions: using scopes for AsyncLocalStorage, an end parameter for Buffer, permission.drop and a new --permission-audit flag, package maps support in the loader, a new node:stream/iter module, context.log() in the test runner, and WebAssembly JSPI enabled. It also updates root certificates to NSS 3.125 and bundles numerous dependency upgrades (npm 11.19.0, ngtcp2, nghttp3, c-ares, sqlite, timezone data) plus a long list of bug fixes across crypto, buffer, http, http2, quic, and net modules.

The UK government has set 2032 as a target date for switching off Freeview digital terrestrial TV broadcasting, moving television delivery entirely to internet-based streaming with an initial set-top-box requirement. This mirrors a broader European decline in over-the-air broadcast media, including the BBC's earlier shutdown of long wave and AM transmissions. Unlike past analog shutoffs, this move retires the very digital multiplex system (DVB-T/ATSC) that replaced analog TV roughly fifteen years ago, despite it still being widely used.

Inertia.js v3.7.0 adds a cancelOnUnmount attribute and a cancel method to the Form component so in-flight submissions can be aborted when a form unmounts or via a button click. usePoll now exposes a reactive polling value across Vue, React, and Svelte. Once props no longer lose their value during instant visits, and navigation no longer cancels background async visits aimed at other pages. Three fixes address a React back_forward stale-props bug, prop identity issues in replaceProp/appendToProp/prependToProp, and a Form unmount crash in React.

Building on an earlier post advocating two-state (rather than tri-state) dark mode toggles, the author now argues that most websites shouldn't have a persistent dark mode toggle at all — the setting should default to following the OS and live in a settings panel instead. The piece responds point by point to Bramus's counter-argument for tri-state toggles (a scenario involving OS auto-switching plus reverted selections), calling it rare, cheaply recoverable, and a case of developers overweighting their own edge cases (IKEA effect meeting false-consensus bias). It also surveys community-designed alternative toggles (Vale's 3-in-2 design,

PostgreSQL 19 introduces four new system views for observability: pg_stat_lock provides cumulative cluster-wide lock contention statistics per lock type, including a fastpath_exceeded counter useful for partition-heavy workloads; pg_stat_recovery gives a single atomic snapshot of standby recovery state (replay LSNs, timelines, pause state, promotion status), replacing the need to combine several inconsistent functions;pg_stat_autovacuum_sc exposes the new per-table scoring system (based on XID age, multixact age, dead tuples, inserts, and analyze staleness) that now determines autovacuum table processing order, replacing the old pg_class ordering; and pg_dsm_registry_allocations lists dynamic shared memory registry entries (name, type, size) used by extensions that no longer need shared_preload_libraries and a restart. The piece walks through each view's schema and runs live demo queries showing sample output. PostgreSQL 19 is still in beta and details may change before GA.

NestJS 12 comes with some solid updates, no doubt about that. But if you haven’t looked at the new observability features yet, it is worth a close look.
Setting up APM tools in Node has always felt a bit clunky. Most agents sit outside the app, monkey-patching HTTP drivers and database packages to guess what is happening under the hood. It works, but you usually lose framework context along the way.
Full Article : https://lnkd.in/p/gP53bYmC

Svelte 5.57 adds new SvelteMap methods (getOrInsert, getOrInsertComputed), a createContext has function, select defaultValue support, and new svelte/server type exports. SvelteKit 3's next release candidate continues iterating with several breaking changes including reworked cross-page form actions, split Vite plugin hooks, defineParams relocation, and route filtering for test files. The sv CLI replaces its mcp add-on with a broader ai-tools add-on and ships a task-based sveltekit-3 migration command that rewrites $lib imports to #lib and bumps dependencies. The roundup also covers stable SvelteKit 2.x patches, language tools updates, and a community showcase of Svelte apps, UI libraries, and dev tools.

Tailscale is expanding from a network you configure into a platform you build with and on. The tsnet Go library lets applications embed Tailscale connectivity directly, giving each app its own tailnet identity, MagicDNS name, and automatic TLS certificates without opening ports or managing proxies. A tailscale-rs library is in pre-alpha, promising bindings for Rust, Python, Elixir, and C. On the automation side, the Tailnets API lets teams provision isolated tailnets on demand for per-customer or per-test isolation, and the same APIs power a new admin console so ACL updates, key rotation, and provisioning can be scripted rather than clicked. A new Declarative Node Sharing feature turns manual cross-tailnet sharing into GitOps-managed policy, currently available via waitlist.

Bun v1.4.2 patches two regressions introduced in v1.4.1: a bun build variable name collision that broke Elysia imports with a SyntaxError, and an AsyncLocalStorage memory leak affecting timers and promises created inside store.exit() or nested store.run(). It also fixes a worker_threads 'online' event ordering bug that caused @discordjs/ws to hang, adds CMYK/YCCK JPEG decoding support to Bun.Image, pulls in roughly 350 upstream WebKit/JavaScriptCore commits fixing Intl, TypedArray, and Proxy correctness issues, and resolves several crash and hang bugs including a rare JIT crash, a musl GC crash, a bun install panic, and a double-close file descriptor bug on Linux

Trendyol's product content team details a phased, zero-downtime migration of five 'helper bucket' datasets (2.24 billion documents across two clusters) from Couchbase to PostgreSQL to cut infrastructure costs while preserving read performance. The strategy combined dual-writes via Kafka consumers, a custom CDC-based migrator tool for historical backfill, and feature-flagged cutover of read traffic. Key production challenges included a mysterious TPS spike traced to PgBouncer's server_reset_query_always setting, a connection-limit incident causing a primary node failover, and a hidden scaling issue where PgBouncer's own horizontal autoscaling multiplied backend connections beyond expectations (20 pods × 150 default_pool_size = 3000 potential connections). Final production benchmarks showed stable P50 latency and only a brief P99 spike (200ms to 400ms) under peak load, validating the migration.