Skip to content
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

New content property in tailwind.config does not work if only one extension (.tsx) is provided #6394

Closed
jvidalv opened this issue Dec 11, 2021 · 1 comment · Fixed by #6449
Assignees

Comments

@jvidalv
Copy link

jvidalv commented Dec 11, 2021

What version of Tailwind CSS are you using?
v3.0.1

What build tool (or framework if it abstracts the build tool) are you using?

Vite 2.6.10
Postcss 8.3.11

What version of Node.js are you using?

v14.6.X

What operating system are you using?

MacOS

Describe your issue

So, I have a React + TypeScript project, this morning I moved into Tailwind v3 and changed purge to content. My surprise came when classes disappeared. Felt like Tailwind was not parsing the files in search for the classNames.

First, ALL my classes are inside .tsx files.

This is my config file that does not work (And did work prior to v3):

image

This is the config file that DOES work:

image

For content to work as before, It must have more than one extension, it does not matter which, but must be more than one, see this example, this also works:

image

Seems like a big bug to me.

@bolshoytoster
Copy link

Does it work when you remove the curly brackets?

i.e. "./src/**/*.tsx"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants