Summary
vite.config.js is unreachable, unbuildable dead code:
- It imports
./plugins/marketplace.js (vite.config.js:14). plugins/ does not exist in the repo.
- Its rollup input is
index.html at the repo root. That file does not exist either — the landing page is src/pages/index.astro.
- No npm script invokes
vite build/vite dev; every script goes through astro or scripts/build-vite.js.
So running anything against it fails immediately at module resolution. It is also the only consumer of MP_PREFIX, which is why that flag looks wired up when it isn't (see the --path-prefix issue).
CLAUDE.md documents it as a live half of a "Two Build Configs" architecture:
- vite.config.js — standalone Vite config with custom
marketplacePlugin from plugins/marketplace.js, base /, used for the non-Astro build path
There is no non-Astro build path. This is actively misleading for anyone (human or agent) reading the docs before touching the build.
Suggested fix
Delete vite.config.js and remove the "Two Build Configs" section from CLAUDE.md, leaving astro.config.mjs documented as the single config. If a non-Astro path is genuinely planned, keep the file but move it somewhere clearly marked as unimplemented and say so in the docs.
Summary
vite.config.jsis unreachable, unbuildable dead code:./plugins/marketplace.js(vite.config.js:14).plugins/does not exist in the repo.index.htmlat the repo root. That file does not exist either — the landing page issrc/pages/index.astro.vite build/vite dev; every script goes throughastroorscripts/build-vite.js.So running anything against it fails immediately at module resolution. It is also the only consumer of
MP_PREFIX, which is why that flag looks wired up when it isn't (see the--path-prefixissue).CLAUDE.mddocuments it as a live half of a "Two Build Configs" architecture:There is no non-Astro build path. This is actively misleading for anyone (human or agent) reading the docs before touching the build.
Suggested fix
Delete
vite.config.jsand remove the "Two Build Configs" section fromCLAUDE.md, leavingastro.config.mjsdocumented as the single config. If a non-Astro path is genuinely planned, keep the file but move it somewhere clearly marked as unimplemented and say so in the docs.