Document Vite to Next.js migration path for ui-kit consumers#152
Open
policyengine[bot] wants to merge 1 commit into
Open
Document Vite to Next.js migration path for ui-kit consumers#152policyengine[bot] wants to merge 1 commit into
policyengine[bot] wants to merge 1 commit into
Conversation
Add migration checklist covering framework transition while preserving ui-kit styling setup. Based on github-wrapped PR #2 migration from Vite + React 19 to Next.js 16 App Router. Key migration steps: - Remove Vite config and index.html - Switch from @tailwindcss/vite to @tailwindcss/postcss - Create postcss.config.mjs - Restructure entry points (main.jsx → layout.tsx + page.jsx) - Fix environment variable references (import.meta.env → process.env) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
Adds migration checklist to
policyengine-ui-kit-consumer-skillfor converting Vite projects to Next.js while preserving ui-kit styling setup.Context
Based on learnings from github-wrapped#2, which migrated from Vite + React 19 to Next.js 16 App Router. The migration involved several framework-specific changes that aren't currently documented in the skill.
Changes
Why This Helps
Future sessions working on PolicyEngine tools that start as Vite prototypes and grow into Next.js apps will have a clear migration path that preserves the ui-kit styling setup.
🤖 Generated with Claude Code