JavaScript Weekly #778 Digest

JavaScript Weekly #778 Digest

Published March 24, 2026 | Edited by Peter Cooper (Cooperpress) Read the issue online


πŸ”Ά Top stories

TypeScript 6.0 bridges the JavaScript compiler and its Go successor

devblogs.microsoft.com

TypeScript 6.0 is the last major release built on the current JavaScript codebase. Its changes prepare projects for the compiler rewrite in Go scheduled for 7.0.

What changed

  • The defaults now include strict: true, module: esnext, rootDir: . and types: []. The compiler no longer automatically loads node_modules/@types. With types: [], many Node.js projects will need to set "types": ["node"] explicitly.
  • Deprecations include target: es5, AMD/UMD/SystemJS module output, --baseUrl, --outFile and the old --moduleResolution node. The import ... assert {} syntax has also been removed.
  • The --stableTypeOrdering flag makes 6.0 order types like 7.0 so you can spot differences in inference before upgrading.
  • New features include Temporal API types, RegExp.escape, #/ subpath imports and reduced context sensitivity for functions without a this parameter.

The Go-native 7.0 compiler, previously codenamed Project Corsa, targets speedups of up to 10Γ—. Microsoft is pursuing the benefits of native execution and shared-memory multithreading. The team says 7.0 is already close to completion. Nightly builds are available through npm and a VS Code extension.

πŸ’‘ Insight

  • Watch the new types: [] default. A Node.js build that relies on implicit types may fail until you add "types": ["node"] to tsconfig.json. Many projects already enable strict: true, so that default should be less disruptive.
  • The migration has two steps. In 6.0, ignoreDeprecations: "6.0" keeps deprecated options working. They go away in 7.0. Try --stableTypeOrdering early to see where inference changes.
  • The compiler itself is joining the wider shift toward native JavaScript tooling already seen with esbuild and Turbopack.

Edge.js runs Node.js apps in a WebAssembly sandbox without Docker

wasmer.io

Wasmer announced an alpha runtime that runs unmodified Node.js applications in a WASM sandbox. Its approach differs from Deno and Cloudflare Workers.

How the runtime works

  • The JavaScript engine runs natively. WASIX sandboxes system calls and native modules, avoiding much of the overhead of compiling the entire runtime to WASM.
  • The engine is pluggable. Choose V8, JavaScriptCore or QuickJS.
  • Edge.js targets Node.js v24 compatibility, with the same underlying dependencies, including libuv, simdutf, ada, llhttp and ncrypto.
  • Use edge --safe for full sandbox mode. Commands such as edge node myfile.js and edge pnpm run dev wrap existing workflows.

Wasmer reports 70–95% of native Node.js performance in sandbox mode and is still working on it.

Potential uses include isolating AI agents and MCP servers, edge computing, and serverless deployments without containers.

πŸ’‘ Insight

  • The design concentrates isolation where code reaches the OS, such as file I/O and networking. JavaScript execution itself can stay in the engine.
  • That could give tools that run arbitrary Node.js code, including MCP servers and Claude Code workflows, a security boundary without requiring Docker.

pnpm 11 Beta 0 introduces a SQLite store, SBOMs and new configuration

GitHub Release

What changed

  • Store metadata moves from JSON files to SQLite. With a msgpack index, reading and writing small blobs (<100 KiB) gets faster.
  • pnpm sbom generates a software bill of materials in CycloneDX 1.7 or SPDX 2.3 format. This first-party support anticipates the EU Cyber Resilience Act and includes --prod, --dev and --filter.
  • pnpm-workspace.yaml gains per-package settings through packageConfigs and explicit approval for package builds through allowBuilds.
  • The beta adds four commands in total, including sbom.

A co-lead of the OWASP CycloneDX project reviewed the implementation and pointed out issues in npm's sbom output that pnpm could avoid.

πŸ’‘ Insight

  • Projects with native builds, including those using electron, should review their allowBuilds configuration when upgrading to pnpm 11.
  • SBOMs are becoming more important for supply-chain security. This is a good opportunity to consider generating them in CI/CD.

πŸ“‹ In brief

  • πŸ€– Debate over AI-generated contributions to Node.js core. The io.js fork's founder, indutny, started a petition opposing AI-assisted contributions. Core implementation work involving LLM-generated code has divided the community.
  • 😒 Departures from Deno. Several employees announced they were leaving, including Preact's Marvin Hagemeyer. Josh Collinsworth said Deno was going through a difficult period and would continue.
  • πŸ“— Chibivue is an online book and code project for learning Vue.js by building a minimal implementation yourself.

πŸ“¦ Releases

Next.js 16.2

nextjs.org

  • next dev starts around 400% faster (an 87% improvement over 16.1).
  • RSC payload deserialization is up to 350% faster. A two-step process replaces the JSON.parse reviver.
  • HTML rendering is 25–60% faster in real applications.
  • Server Fast Refresh reworks server-side hot module replacement, with reported gains of 67–100%.
  • New tools include next start --inspect, a hydration diff indicator, and server function logging.
  • AI agent tooling includes AGENTS.md and the experimental next-browser DevTools.
  • Turbopack received over 200 bug fixes.

πŸ’‘ Insight

  • In V8, a JSON.parse reviver crosses the C++/JavaScript boundary for every key-value pair. Even a no-op callback can make parsing four times slower. React switched to JSON.parse() followed by a recursive walk in JavaScript. Next.js users now benefit from that change.

Other releases


πŸ“– Articles and videos


πŸ›  Code and tools


🌐 Around the ecosystem

  • πŸ€– How VS Code builds with AI. The team shares how it uses AI throughout its weekly release cycle, from issue management to shipping.
  • πŸ”’ Secretlint is a dedicated linter for spotting secrets in a repository.
  • πŸ“œ Rob Pike's 5 Rules of Programming (1989). The Go and UTF-8 co-creator's rules went viral this week and still hold up in 2026.
  • 🧠 Comprehension Debt. Addy Osmani asks a different question about coding with AI agents: how well do we understand the code we ship?

Three themes from this issue

1. Crossings have a cost

The TypeScript 6.0 to 7.0 transition involves the JS/Go boundary, Edge.js the JS/OS boundary, and the parser rewrite the JS/WASM boundary. Each raises the question of how often to cross it. Next.js 16.2 also gained speed by eliminating C++/JS crossings in the JSON.parse reviver.

2. The ecosystem is changing hands

Departures from Deno, the debate over AI code in Node.js core, and the TypeScript rewrite in Go all point to a transitional period for JavaScript and TypeScript.

3. Understanding what we ship

Addy Osmani's comprehension debt, Garbutt's question about why a dependency exists, and Pike's rules from 1989 share a concern: as AI accelerates code generation, what do the people shipping that code actually understand?