fix(nextjs): add setup generator for Tailwind CSS fixes absolute pathing #30192
+444
−4
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
View your CI Pipeline Execution ↗ for commit 99d592f.
☁️ Nx Cloud last updated this comment at |
ndcunningham
force-pushed
the
fix/nextjs-tailwind-relative-paths
branch
from
75ea4b6 to
c00c67a
Compare
4 tasks
ndcunningham
force-pushed
the
fix/nextjs-tailwind-relative-paths
branch
from
c00c67a to
7927be8
Compare
jaysoo
approved these changes
Feb 26, 2025
ndcunningham
force-pushed
the
fix/nextjs-tailwind-relative-paths
branch
2 times, most recently
from
157c8a2 to
dec733d
Compare
ndcunningham
force-pushed
the
fix/nextjs-tailwind-relative-paths
branch
from
dec733d to
99d592f
Compare
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
When we generate a Next.js application with tailwindcss running with
--turbofails due to how the globs are defined insidetailwind.config.js.Expected Behavior
Relative paths a singular globs are required with this change tailwind should work with HMR using
--turboRelated Issue(s)
Fixes #29946