feat(init): onboard MDX and Tailwind v4 apps on first build - #3239
Open
JamesbbBriz wants to merge 2 commits into
Open
feat(init): onboard MDX and Tailwind v4 apps on first build#3239JamesbbBriz wants to merge 2 commits into
JamesbbBriz wants to merge 2 commits into
Conversation
Migrating a Next.js app that uses MDX pages and Tailwind v4 currently fails twice before the first successful build: - @mdx-js/rollup is required for the documented MDX auto-injection but was never installed by init - Tailwind v4 configured through postcss.config string plugins cannot resolve under Vite; it needs @tailwindcss/vite in the config detectProject now reports hasTailwind (tailwindcss dependency); init installs @mdx-js/rollup / @tailwindcss/vite for detected frameworks and generates vite configs that wire tailwindcss() for both platforms. The next.config webpack-ignore warning now explains that Vite resolves TS/TSX natively, since every Payload-style extensionAlias config trips it today. Output for projects without Tailwind stays byte-identical.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
commit: |
Contributor
Performance benchmarksCompared 1 improved · 0 regressed · 5 within ±1.5%
View detailed results and traces 🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head |
The first pass rewrapped a dozen untouched call sites onto multiple lines. main is format-clean with the single-line forms, so the rewraps were pure review noise.
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.
Migrating a Next.js app that uses MDX pages and Tailwind v4 currently fails twice before the first successful build:
@mdx-js/rollupis required for the documented MDX auto-injection but was never installed byinitENOENT ... tailwindcssfrom postcss-import); it needs@tailwindcss/vitein the configdetectProjectnow reportshasTailwind(tailwindcss dependency); init installs@mdx-js/rollup/@tailwindcss/vitefor detected frameworks and generates vite configs that wiretailwindcss()for both platforms. Thenext.configwebpack-ignore warning now explains that Vite resolves TS/TSX natively, since every Payload-styleextensionAliasconfig trips it today. Output for projects without Tailwind stays byte-identical.Fixes #3240