Svelte

Why it's ranked here

Worth ten minutes if you want to see how a compiler-first framework is actually assembled. The pipeline is three genuinely separable stages, and the analysis stage dispatches to 61 node visitors, which is the real cost of turning template syntax into static reactivity. The counterweight is surface area: the published package declares 23 export entry points, several of them marked internal or legacy. This is not a dependency you skim. Governance is written down rather than implied: MIT license, monthly maintainer meetings, a public request-for-comments process, and a stated policy of one major effort at a time.

What's good

The compile path is legible. Parsing, analysis and code generation are separate stages with separate exported functions, so you can parse a component without generating output, or ask for a syntax tree alone. Server and browser output come from one shared analysis. Conditional exports pick the browser build in browsers and the server build elsewhere, so bundlers resolve correctly without configuration. The runtime dependency list is short and specific: a JavaScript parser, a source map codec, a tree walker, a class name helper. Contribution rules cover snapshot updating, naming conventions and a required test plan per pull request.

Tradeoffs

Two costs stand out. First, the published surface carries an explicit legacy lane beside the modern one, plus internal entry points consumers are told not to import but can, and a parser option whose default is scheduled to flip in the next major and be removed in the one after. Second, this is a monorepo wired to a single package manager: the workspace file, the scripts and the contributing guide all assume it, and running the browser tests needs a separately installed Chromium. There is no drop-in script tag here. A build step is the whole premise.

How to use it well

Two audiences. Application teams who want compiled output instead of a shipped runtime library, and tool authors who need to parse or transform component files programmatically, since the compiler is a public entry point with a separate build for older module consumers. The project points application developers at its companion framework for routing, data loading and deployment, none of which this package provides. It also gives you no component library, no state store beyond its own reactivity primitives, and no styling system past per-component scoping.

Observed

License

MIT, declared in both the monorepo root and the published package

Language

JavaScript with JSDoc type annotations; type declarations generated and checked in

Compiler pipeline

Three numbered phases: parse, analyze, transform

Analysis breadth

61 node-type visitors registered in packages/svelte/src/compiler/phases/2-analyze/index.js

Package surface

23 export entry points in packages/svelte/package.json, including internal, legacy and flag paths

Interfaces

Library plus a programmatic compiler API; browser and server builds selected by export conditions

Platform support

Node 18 or newer declared as the engine floor

Repo shape

pnpm workspace monorepo over packages and playgrounds, per pnpm-workspace.yaml

Supply chain policy

pnpm-workspace.yaml enforces a 2880-minute minimum release age and blocks exotic subdependencies

Testing surface

Vitest suites plus Playwright Chromium, with snapshot regeneration documented in CONTRIBUTING.md

Agent guidance

AGENTS.md ships in the repo and requires the pull request template and a full test run