Allow support for non-jsx React files in Tailwind config #159
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
|
Support for this indicated here: https://tailwindcss.com/docs/configuration#content |
|
Hi @morris14, With the upcoming switch to Vite in #158, new projects will need to use a Do you know of any common scenarios where a |
|
@jessarcher that makes sense, thanks for clarifying! I guess devs who are used to using .js will just need to get used to using .jsx 😄 Thanks 👍 |
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.
Not all developers will use .jsx as the file extension for their React components. I was editing a React component recently with a .js prefix and realised my tailwind classes weren't getting generated correctly. This should help support that.