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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor tailwind integration setup #5717
Refactor tailwind integration setup #5717
Changes from 1 commit
6949220
d3af05a
8d604da
13387d4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bluwy Setting an inline PostCSS config in Vite, has the effect that Vite no longer looks for
postcss.config.cjs
.See:
That results in by adding the Tailwind Integration 3.0.0-beta.x,
postcss.config.cjs
no longer work as described in the Astro Docs.https://docs.astro.build/en/guides/styling/#postcss
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm that's true, but I think that happens before this PR too as Astro was assigning to the property internally:
https://github.com/withastro/astro/pull/5717/files#diff-025f8338e5be413b0f65c74bc50d6484c6bc9bb4f78847da0ba896b8e9569390L153-L155
I guess for the tailwind integration we need to read
postcss.config.js
too to resolve this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirming, trying latest
@beta
packages makes Tailwind to ignorepostcss.config.js
(f.e. to enable nesting)Seem to be addressed in: #5908
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Came up with a possible fix for the issue, but I'm hitting another issue. Applying changes to the
postcss.config.js
file only has effect after restarting the dev server.I just wanted to know if it was an issue before, so that it will get addressed in another PR and doesn't block the current one.
Any ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was looking at the old code. I'd be fine merging it first, then handle the restart later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, thanks!