chore(playground): replace Astro with Vite + React#20
Closed
arzafran wants to merge 2 commits into
Closed
Conversation
The Astro playground was the repo's entire dependency/staleness surface: ~365 of the lockfile's packages came from astro + @astrojs/* (language server, vite, esbuild, sharp, shiki, …) to render 4 demo pages, and every Dependabot advisory originated there. The published library is untouched (zero runtime deps, not affected by playground tooling). Replace it with a minimal Vite multi-page app: - vite.config.ts: MPA (index/core/react/landing) + @vitejs/plugin-react, preserving the tempus / tempus/react / tempus/profiler source aliases so local dev still HMRs against packages/ source. - index/core/react/landing .html entries replicating the old layout nav + per-page markup (landing.html ports the full hero prototype). - react/main.tsx mounts <App/>; app.tsx now renders frame state. - drop astro, @astrojs/react, @astrojs/check, astro.config.mjs, www/*.astro, core/browser.js. - move lottie-web + motion from root devDeps into the playground (folds #18). Lockfile: 629 -> 264 packages (-365). astro/@astrojs fully gone. Closes #19.
arzafran
force-pushed
the
chore/vite-playground
branch
from
302258a to
5e356cb
Compare
After removing Astro, the remaining 10 advisories were all transitive under tsup (the library's build tool, a dev dependency): glob, minimatch, rollup, picomatch, esbuild, brace-expansion. - bump tsup 8.3.6 → 8.5.1 - pnpm.overrides pin patched versions of the transitive leaves `pnpm audit` now reports 0. The published library has zero runtime deps, so none of these ever reached consumers; this only cleans the dev tree and the Dependabot dashboard. Verified: library + playground build green, core bundle byte-identical (1985 B gz).
This was referenced Jun 19, 2026
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Replaces the Astro playground with a minimal Vite + React multi-page app. The Astro toolchain was the repo's entire dependency and staleness surface — hundreds of transitive packages (language server, vite, esbuild, sharp, shiki, …) to render 4 demo pages, and the origin of every Dependabot advisory. The published
tempuspackage (zero runtime deps, 1.98 kB gzipped) is completely unaffected; the playground is dev-only and not published.This is why we closed the astro-upgrade PRs (#12/#14/#16) — rather than chase astro majors, we remove it. Mirrors darkroomengineering/hamo#14.
Result
astroand all@astrojs/*gone.index,core(vanilla TS + profiler),landing(the full hero prototype),react.Summary
vite.config.ts: MPA inputs (4 HTML entries) +@vitejs/plugin-react, preserving thetempus/tempus/react/tempus/profilersource aliases so local dev still HMRs againstpackages/source (validates the published entry points).index/core/react/landing.htmlreplicate the old layout nav + per-page markup;landing.htmlports the full hero prototype (its 4 driven element IDs —load,metro-arm,scope,toggle— verified againsthero.ts).react/main.tsxmounts<App/>;app.tsxnow renders frame state (it was a no-render placeholder, whichtsccorrectly rejects as a JSX component — Astro'sclient:onlynever type-checked that).astro,@astrojs/react,@astrojs/check,astro.config.mjs,www/*.astro,core/browser.js.lottie-web+motionfrom root devDeps into the playground (onlycore/test.tsuses them) — folds in chore: move playground-only deps out of root #18.Test Plan
pnpm build(library) succeedspnpm --filter playground buildgreen — tsc --noEmit + vite build, all 4 pagespnpm dev:playgroundserves all 4 pages (200) with source aliases resolvinglanding.htmlretains the DOM elementshero.tsdrivesCloses #19. Supersedes #18.