TypeScript goes native: public previews of the Go‑based compiler (Project Corsa)
Key update
Microsoft published the TypeScript Native Previews (Project Corsa): a Go‑based port of the TypeScript compiler and language service available as an npm preview package (exposes the tsgo binary) and a VS Code "TypeScript (Native Preview)" extension. The team reports consistent ~10× improvements on large real‑world projects (type‑checking times and editor project‑load), now including JSX and JavaScript+JSDoc checking, and an LSP‑based editing flow. The previews are explicitly “work in progress”: many editor features and some emit/build flags are still missing and there are known behavioral differences in edge cases.
Why it matters
This is a practical, non‑cosmetic change to TypeScript tooling that immediately alters developer ergonomics and CI economics for large codebases and monorepos. Faster type checking and much lower editor startup latency will reduce iteration time, enable heavier static analysis and larger monorepo workflows, and make on‑the‑fly tooling (refactors, cross‑project queries, AI‑powered assistants) far more responsive. Operationally teams must treat the native build as a different runtime artifact: CI images and dev environments will need to include or install the tsgo binary, and editor integrations rely on the new LSP path (libsyncrpc bridges exist for Node). Because the preview can differ in subtle ways (module resolution, custom transformers, specific --build/emit behaviors), treat adoption as incremental: validate tsgo on representative services/branches, run end‑to‑end tests and type‑sensitive tooling, and plan to update CI/devcontainer images only after you verify parity for your workloads. Long term, this becomes the path to TypeScript 7 and a materially faster developer experience; short term, expect to run the native preview side‑by‑side with the existing JS compiler to surface any compatibility issues.
Source
Read Next
Node.js v25 scheduled for 2025‑10‑15 — semver‑major release imminent
September 30, 2025Node.js v25 is scheduled for October 15, 2025 (commit cutoff 2025‑09‑15). Teams should run CI against the new major, validate native modules, and prepare canary deployments.
Azure Functions Proxies: community support ends 2025‑09‑30 — migrate off Proxies now
September 29, 2025Azure announced Azure Functions Proxies will be unsupported after 2025‑09‑30; teams still using Proxies must inventory and migrate to a supported API surface (APIM, Front Door, or a lightweight reverse proxy) immediately.
NodeShield: runtime SBOM enforcement (CBOM) for Node.js limits supply‑chain attacks with negligible overhead
September 28, 2025A new paper introduces NodeShield, a runtime enforcement system that uses SBOMs extended with per‑dependency capabilities (CBOM) to prevent supply‑chain abuses in Node.js with ~98% effectiveness and <1ms overhead.