Conversation
Refocus the docs on Vite DevTools specifics and consolidate the kit section to the pages a Vite integration actually needs: the plugin hook, the dock system, and the createPluginFromDevframe bridge. The generic mechanics shared with every host framework (RPC, shared state, streaming, json-render, when clauses, terminals, messages, commands, remote client) now defer to the Devframe guide at devfra.me. Also correct a stale API reference in the DTK0033 error page (embeddedVisibility) and add a docs-build job to CI so a broken docs build is caught before it silently leaves the published site on a stale deploy. Fixes #562
@vitejs/devtools
@vitejs/devtools-kit
@vitejs/devtools-oxc
@vitejs/devtools-rolldown
@vitejs/devtools-vite
@vitejs/devtools-vitest
commit: |
… client-context, examples as concise pages Keep the concepts on the docs site with short explanations and examples focused on Vite-plugin usage, linking to devfra.me for the full framework-neutral reference. Streaming, json-render, when-clauses, and remote-client stay deferred to devfra.me.
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
2 participants
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
Reworks the docs to stay focused on Vite DevTools specifics and lean on devfra.me for the framework-neutral Devframe mechanics.
kit/section to the pages a Vite integration actually needs: thedevtools.setupplugin hook, the dock system (with install launchers and theviteplusgroup), and thecreatePluginFromDevframebridge. The introduction now frames Kit as the thin Vite skin over Devframe.remote-demofixture (dogfooded by the core playground) and repointed its generic prose at the Devframe client guide.DTK0033error page (visibility→embeddedVisibility), the same removed option that website docs stale #562 flags.Linked Issues
Fixes #562
Additional context
The website serves docs generated from this repo via Netlify (
pnpm run build && pnpm run docs:build). The getting-started guide already used the correctedembeddedVisibility, so merging this (which touches docs) regenerates the site; the new CI job guards against future silent staleness. Verified locally withpnpm -C docs run docs:build(no dead links).This PR was created with the help of an agent.