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
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: .andtypes: []. The compiler no longer automatically loadsnode_modules/@types. Withtypes: [], many Node.js projects will need to set"types": ["node"]explicitly. - Deprecations include
target: es5, AMD/UMD/SystemJS module output,--baseUrl,--outFileand the old--moduleResolution node. Theimport ... assert {}syntax has also been removed. - The
--stableTypeOrderingflag 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 athisparameter.
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 enablestrict: 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--stableTypeOrderingearly 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 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 --safefor full sandbox mode. Commands such asedge node myfile.jsandedge pnpm run devwrap 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
What changed
- Store metadata moves from JSON files to SQLite. With a msgpack index, reading and writing small blobs (<100 KiB) gets faster.
pnpm sbomgenerates 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,--devand--filter.pnpm-workspace.yamlgains per-package settings throughpackageConfigsand explicit approval for package builds throughallowBuilds.- 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 theirallowBuildsconfiguration 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
next devstarts around 400% faster (an 87% improvement over 16.1).- RSC payload deserialization is up to 350% faster. A two-step process replaces the
JSON.parsereviver. - 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.mdand the experimentalnext-browserDevTools. - Turbopack received over 200 bug fixes.
π‘ Insight
- In V8, a
JSON.parsereviver crosses the C++/JavaScript boundary for every key-value pair. Even a no-op callback can make parsing four times slower. React switched toJSON.parse()followed by a recursive walk in JavaScript. Next.js users now benefit from that change.
Other releases
- Storybook 10.3.0 supports Vite 8, Next.js 16.2 and ESLint 10. It also previews an MCP server for React development.
- β οΈ Upcoming Node.js security releases will address nine vulnerabilities across all maintained versions.
- Deno 2.7.6 adds automatic CJS/ESM detection for
deno evaland interactive SVG flame graphs with--cpu-prof-flamegraph. - Bun 1.3.11, Valibot 1.3, ESLint 10.1
π Articles and videos
- π The Three Pillars of JavaScript Bloat. James Garbutt of e18e groups npm bloat into three categories: ES3-era compatibility packages like
is-string, single-purpose packages in the style of Sindre Sorhus (such as the one-lineshebang-regex), and obsolete ponyfills (such asglobalthis, still downloaded 49 million times a week despite native support arriving in 2019). He suggests auditing dependencies with the e18e CLI or knip. - π Rewriting a Rust and WASM parser in TypeScript made it faster. Crossings between WASM and JavaScript were so expensive that a pure JavaScript implementation ran 2β4Γ faster in many cases. Boundary costs matter here just as they do in Edge.js.
- π Benchmarking React SSR frameworks. Matteo Collina compared TanStack Start, React Router and Next.js under load. The results led to patches in both TanStack and React.
- π¬ Two React design choices developers dislike but cannot avoid. Deferred state commits and dependency arrays make more sense when you consider timing. Ryan Carniato explains how Solid's synchronous signals let it sidestep them.
- π JavaScript Thinks Everything's a Date. A reminder of why progress on Temporal is worth celebrating.
- π A Complete Guide to Bookmarklets. CSS-Tricks looks at JavaScript snippets you can save as bookmarks.
- πΊ How to Burn $30M on a JavaScript Framework. Fireship revisits the 2012 famo.us project in five minutes.
- π Node.js worker threads have problems, but they were right for us. Inngest shares its experience.
π Code and tools
- ArrowJS 1.0 is a fast reactive UI runtime built on ES modules, template literals and the DOM. It can isolate components in a WASM sandbox. First introduced in 2022 by the creator of FormKit, it has now reached 1.0.
- Sugar High 1.0 is a lightweight JSX syntax highlighter. It works without React and supports CSS themes. GitHub
- htmlparser2 12.0 is a fast HTML parser.
- vue-audio-visual 3.1 visualizes the Web Audio API in Vue 3.
- Svelte SEO 2.1 handles meta tags, Open Graph and JSON-LD for Svelte apps.
- pnpm/action-setup 5.0 is the pnpm GitHub Action, now supporting Node.js v24.
- React Joyride 3.0 adds guided tours to React apps.
- EventCalendar 5.5, Maz UI 4.9, Mediabunny 1.40
π 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?
