refactor(ranvi): extract the builder into its own published package

[chaxus]

The builder had grown into a general-purpose library wearing a component library's clothes: 1,831 lines, a 434-line manual, 345 tests, and exactly one external import. Anyone who wanted framework-free reactive DOM had to install ranui — and with it dash.js, hls.js, mpegts.js, mermaid and temml: 242 MB of transitive dependencies for a file that depends on one function. ranpress could not use it at all for that reason.

It is ranvi now, depending only on ranuts.

ranui's behaviour is unchanged — that was the acceptance test

All 1,641 remaining ranui tests pass without a single edit.

	before	after
ranui unit	1,732	1,565
ranui ssr	254	76
ranvi	—	345
total	1,986	1,986

None lost. The one further difference — 1,566 → 1,565 — is docs.references, which generates a case per doc file in ranui, and ranui now has one fewer doc.

How the surface was kept identical

• 84 of the 90 internal imports go through @/utils/builder, so that path stays and re-exports ranvi. Not one of those files changed.
• The six that reached past it (./builder/core, ./builder/signal, ./builder/env) now name ranvi directly.
• builder.ts, the published ranui/builder entry, keeps enumerating every export by name rather than forwarding wholesale — a star would also carry whatever ranvi adds next, quietly widening ranui's public API. (package-exports.source enforces this, and caught it when the word appeared in a comment.)

Build output, checked in both shapes

They differ, and both had to be right:

• ES build externalises ranvi — it is a runtime dependency, so consumers get it through npm. dist/builder.js is now a 1.4 kB re-export.
• IIFE bundles inline it, as they must. Verified no standalone bundle contains a bare import of it; the only occurrence of the string is inside an error message.

Packaging

ranvi exports TypeScript source to workspace consumers and swaps in dist through publishConfig at pack time, so pnpm -F ranui build needs no build-order dependency on it.

That does mean consumers type-check this source — which immediately found a bare import.meta.env.DEV that only compiles where Vite's ambient types are declared. It is a local helper now. This is the kind of thing that would otherwise have been discovered by the first person to install the package.

Found on the way

• ShadowBuilder kept a private options field that nothing ever read — taken in the constructor, assigned, never used.
• Error strings still said "ranui": a cyclic-dependency message and a duplicate-key warning now name the package they come from.
• test/readme.test.ts is new. The manual's import lines were rewritten from ranui/builder to ranvi mechanically, and nothing was checking that the names in them exist. A manual that tells a reader to import something that does not exist is worse than no manual — they assume they are holding it wrong. 21 names checked.

Verification

tsc across 8 packages, 3,145 tests, verify:design across 3 packages, verify-packages (14 declared), prettier, and both ranui and ranvi builds.

🤖 Generated with Claude Code

https://claude.ai/code/session_019pjSL6jGCw2wmBLhCAW35d

[cloudflare-workers-and-pages]

Deploying ran with    Cloudflare Pages

Latest commit:	e09f322
Status:	✅  Deploy successful!
Preview URL:	https://a95ba4f7.ran-4ty.pages.dev
Branch Preview URL:	https://refactor-extract-ranview.ran-4ty.pages.dev

View logs