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

.gitignore is too powerful and cannot be stopped #16920

Open
kingmesal opened this issue Mar 3, 2025 · 1 comment
Open

.gitignore is too powerful and cannot be stopped #16920

kingmesal opened this issue Mar 3, 2025 · 1 comment

Comments

@kingmesal
Copy link

What version of Tailwind CSS are you using?

v4.0.9

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

postcss: 8.5.3

What version of Node.js are you using?

Node: v22.11.0
Bun: 1.2.5

What browser are you using?

N/A

What operating system are you using?

Linux

Describe your issue

I have a mulitple wildcard patterns like special-*.hbs in my .gitignore and I cannot find a way to tell tailwind v4 to ignore my gitignore or to be able to specify an @source "../src/special-*.hbs"

Let me explain my process. My toolset copies a bunch of templates into my users site. They match special-*.hbs. These are in the .gitignore because they are not intended to be checked into their repository.

I have tried @import "tailwindcss" source(none); then specify @source "../src"; but the .gitignore is still in effect, which I thought would get turned off using the source(none).

What can I do here?

@kerams
Copy link

kerams commented Mar 7, 2025

Same here. During builds I am generating files which are gitignored, so I'd really love the ability to use source(none) in combination with file globbing like in v3, something like @source "../*.generated.js", or some strict whitelisting with everything else excluded.

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

No branches or pull requests

2 participants