docs: add Builder-to-Vite migration guide#3819
Merged
Merged
Conversation
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.
Fresh 2 projects created with
--builder(or predating the Vite plugin) hadno documented path for switching to the Vite-backed build, so users were
left to diff a freshly generated project against their own. This adds a
"Migrating from the Builder to Vite" section to the existing Vite advanced
doc, walking through the
deno.jsonupdates, thedev.ts→vite.config.tsswap, the new
client.tsentry and CSS move out ofstatic/, the Tailwindplugin switch, and a short verification checklist.
Placed inline in
docs/latest/advanced/vite.mdrather than as a newmigration-guide page so all Vite content stays in one place; no
toc.tschange needed.