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

Content resolution not finding classes inside parametrized Nuxt pages since 6.13.2 #964

Closed
jrutila opened this issue Mar 11, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@jrutila
Copy link
Contributor

jrutila commented Mar 11, 2025

Environment


  • Operating System: Linux
  • Node Version: v18.20.3
  • Nuxt Version: 3.16.0
  • CLI Version: 3.22.5
  • Nitro Version: 2.11.6
  • Package Manager: [email protected]
  • Builder: -
  • User Config: modules, compatibilityDate, future
  • Runtime Modules: @nuxtjs/[email protected]
  • Build Modules: -

Reproduction

https://stackblitz.com/edit/nuxt-ui-yvqyz6kp?file=README.md

Describe the bug

If I have a page route like this /guide/[gameId]/[...guideId].vue the nuxtjs/tailwindcss does not recognize the tailwind classes inside that file. Other pages are recognized. This worked with 6.12.2.

Additional context

No response

Logs

@jrutila jrutila added the bug Something isn't working label Mar 11, 2025
@jrutila
Copy link
Contributor Author

jrutila commented Mar 12, 2025

I tried this with only Vite, Vue and tailwindcss (3.14.7) and the content resolution seems to work with a component named [...comp2].vue.

edit: It didn't, after all. It is about the content glob. **/*.vue will find the [...comp2].vue file. But pages/[...comp2].vue does not match that file.

@jrutila
Copy link
Contributor Author

jrutila commented Mar 12, 2025

I tried with nuxtjs/[email protected] and tailwindcss forced to 3.4.13 (that is the same than in 6.12.2) and the bug persists. So, this would also imply the bug is not in tailwindcss but in this nuxt module.

@ineshbose
Copy link
Collaborator

Hopefully the issue is fixed in nightly version now? 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants