Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Some classes are not working on production build #16172

Closed
dany68 opened this issue Feb 2, 2025 · 3 comments
Closed

Some classes are not working on production build #16172

dany68 opened this issue Feb 2, 2025 · 3 comments

Comments

@dany68
Copy link

dany68 commented Feb 2, 2025

What version of Tailwind CSS are you using?

Tailwind v4.0.3

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

Nuxtjs app with vite

What version of Node.js are you using?

Node v22.12.0

What browser are you using?

The problem occurs on all the major browser: Chrome, Safari, Firefox

What operating system are you using?

macOS

Describe your issue

Hi thanks for your work on the new major version,

On production build with minification of the code some classes are not working. For instance: space-y-*, space-x-*, *:[grid-area:1/1]
On localhost during development there are no such problems.

@wongjn
Copy link
Contributor

wongjn commented Feb 2, 2025

Would you be able to provide a reproducible example please (such as a remotely-hosted git repository)?

@Botato300
Copy link

I had that problem too, I think it is a problem with Vite build.
Issues published in the vite repository: vitejs/vite#18974

@dany68
Copy link
Author

dany68 commented Feb 3, 2025

Thank you @Botato300, it seems to be the same issue. It makes the v4 not really usable in production for the moment.

I would be happy to help, but not sure where to start.

@tailwindlabs tailwindlabs locked and limited conversation to collaborators Feb 3, 2025
@philipp-spiess philipp-spiess converted this issue into discussion #16213 Feb 3, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

4 participants