feat(devframe)!: switch DevTools mount-path convention from /. to /__#315
Merged
feat(devframe)!: switch DevTools mount-path convention from /. to /__#315
/. to /__#315Conversation
Static deploy platforms hide files starting with `.`. Flip the three Nuxt SPA URLs so deployed builds survive Vercel/Netlify publishing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Flip every dot-prefixed path the build output ships into deploy publish dirs: mount path defaults, connection meta, RPC dump dir, client-imports, and the auth URL on the host. Cache paths under node_modules/.* are unaffected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sweep through guides, error pages, skills, READMEs, example BASE_PATH overrides, and the lone test fixture URL. Functional bits (example basePath constants and the kit-plugin test assertion) ride along since they encode the same convention. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
antfu
changed the title
commit: |
After a0188c1 ("do not inline immer"), the bundled `Patch as SharedStatePatch` re-export is collapsed to a plain `SharedStatePatch` in the emitted dts. The snapshot still encoded the inlined form and broke CI on every platform. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
antfu
changed the title
/. to /__
Merged
7 tasks
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.
Description
Static deploy platforms (Vercel, Netlify, Cloudflare Pages, GitHub Pages, …) hide files and directories whose names begin with
.from the served output, so acreateBuildsnapshot of a devtool currently 404s on its own./.connection.jsononce deployed. This PR flips the leading.to__everywhere the convention shows up in deployed URLs and deployed filesystem artifacts — mount-path defaults (/__\${id}/), the three Nuxt SPAs (/__devtools-rolldown/,/__devtools-vite/,/__devtools-self-inspect/), the meta/dump filenames (__connection.json,__rpc-dump/,__client-imports.js,__devtools/), and the matching JSDoc / docs / skills / examples. Cache-only paths (node_modules/.vite/,node_modules/.rolldown/,node_modules/.cache/, MCP storage) and project meta (.gitignore,.vitepress/cache) are deliberately untouched. This is a breaking change for anyone with hardcoded mount-path strings or cached deploy snapshots, but the project is atv0.1.20so the impact surface is small.Linked Issues
Additional context
Split into four atomic commits so each one keeps
pnpm vitest run --project '@*' --project devframe(330 tests / 42 files) green: SPAs first, devframe constants + auth URL + tests next, then JSDoc/comments, then user-facing docs and example basePaths. Verified viapnpm lint(clean) andpnpm build(9/9 turbo tasks). Reviewers may want to focus ondevframe/packages/devframe/src/constants.tsand_shared.ts(the source-of-truth flips that propagate everywhere via constants) and onstatic-serve.test.ts(the deploy-contract guard tests, including the renamed "stray__devtools/directory" regression). One follow-up worth flagging: thevite-devtools build --outDirdefault is still.vite-devtools, which would also be filtered by deploy platforms when co-located with an app's publish dir — left out of this PR per the approved plan, but worth a separate change if/when needed.🤖 Generated with Claude Code