Repository navigation
chore: migrate to TanStack Start - #3
Merged
Merged
Conversation
Dokploy Preview Deployment
|
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
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.
Summary
Migrate Links from Next.js to TanStack Start with Vite and Nitro. Move the page and document metadata into file-based routes, centralize site details, and update CI and setup instructions.
Evidence
After:
pnpm buildproduces client, SSR, and Nitro server output; CI builds before running checks.pnpm build,pnpm format:check,pnpm lint,pnpm typecheck,pnpm knip, andgit diff --check origin/main...HEAD.Merge Danger
Door: two-way
Revert the migration to restore the previous framework and build setup.
Blast Radius: application
Deployment must use the Nitro output and updated environment variable names. The
startscript is replaced bypreview.