[v4] Source glob pattern `./**/*.{js,ts,jsx,tsx,mdx}` does not match Next.js-style catchall route segments like `[...slug]`.

[nicksergeant]

What version of Tailwind CSS are you using?

v4.0.3

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

• Next.js 15.1.6
• PostCSS 8

What version of Node.js are you using?

23.5.0

What browser are you using?

Chrome

What operating system are you using?

macOS

Reproduction URL

https://github.com/nicksergeant/tailwind-v4-dynamic-params/

Describe your issue

If you are disabling automatic detection with:

@import 'tailwindcss' source(none);

and then configuring a glob pattern like this:

@source './**/*.{js,ts,jsx,tsx,mdx}';

Source files in directories such as [...slug] will not be picked up: https://github.com/nicksergeant/tailwind-v4-dynamic-params/blob/main/app/%5B...slug%5D/page.tsx

I'm not sure if this is a bug per se, and I have found this workaround:

@source './**/*.{js,ts,jsx,tsx,mdx}';
@source './[[]**[]]/*.{js,ts,jsx,tsx,mdx}';

Example page showing missing style: https://github.com/nicksergeant/tailwind-v4-dynamic-params/blob/main/app/%5B...slug%5D/page.tsx#L4

But I was surprised that ./**/* was not working to pick those up.

[neoplastic]

Wow. That's the problem I was having, I was wondering why some of the custom classes weren't working in my code.

[nicksergeant]

I'm also not sure if my posted workaround above is actually sufficient. For some reason it seems to be working in my isolated test case above, but not in our larger repo using the same versions.

[neoplastic]

I have a relatively large repo which I upgraded from 3 -> 4 beta -> 4.

Mine's actually happening on a regular routed segments (/my/route/), its probably happening on leaf segments too (/my/route/[id])

I could use some of the old tailwind sizes like h-96 but anything new or calculated wasn't working. Was racking my head around it with some new components over the past couple days.

I had the feeling that it was some of the files weren't being scanned over by tailwind to generate the CSS for it.

If its not working in your larger repo is there some complexity in the path names to your js/ts/etc files?

[nicksergeant]

If its not working in your larger repo is there some complexity in the path names to your js/ts/etc files?

Yeah I'm not sure - we actually only have a single catchall route in the whole repo ([...slug]). We do have some dynamic routes like [slug] but we've only used the catchall once.

And I haven't noticed any Tailwind issues with the non-catchall routes (at least yet... hard to tell with 3,700 files 😆).

[philipp-spiess]

Hey! Thanks for the bug report, we could track this down to an issue in the glob-match library. Keeping you posted on any updated findings!

[nicksergeant]

@philipp-spiess thanks! Should we add an issue to the https://github.com/devongovett/glob-match repo?

Edit: it seems that this library also has open PRs on bugs that haven't been merged in some time, and this lib hasn't seen a commit in 2 years 😬.

[philipp-spiess]

@nicksergeant Yeah I reached out to Devon to see if he has time to prioritize looking into any of the open PRs since either of them fixes the issue you are seeing. If we don't hear back we'll probably going to inline the library with the fix applied.

[nicksergeant]

Oh awesome! Thanks 🙏

[philipp-spiess]

Should be fixed in the release that went out today 👍

[nicksergeant]

Amazing!