Postcss / hot reload build of tailwind-config classes not working

Open
#1,001 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, nuxt, tailwindcss

Research direction

Review the tailwind.config.js and Nuxt configuration, especially the postcss and @nuxtjs/tailwindcss settings. First establish a minimal reproduction for hot compilation on Windows using the listed Nuxt, Node, and module versions. Done means custom Tailwind classes update correctly during development hot reload.

Written by the indexing model from the issue text.

Description

bug need-repro
Environment

  • Operating System: Windows_NT
  • Node Version: v20.19.0
  • Nuxt Version: 3.17.5
  • CLI Version: 3.25.1
  • Nitro Version: 2.11.12
  • Package Manager: npm@10.8.2
  • Builder: -
  • User Config: compatibilityDate, devtools, modules, primevue, googleFonts, app, css, postcss, runtimeConfig, supabase
  • Runtime Modules: @nuxt/content@3.6.0, @primevue/nuxt-module@4.3.5, @nuxtjs/google-fonts@3.2.0, @nuxtjs/tailwindcss@7.0.0-beta.0, @nuxtjs/supabase@1.5.2
  • Build Modules: -
Reproduction

No response

Describe the bug

Somehow Hot compiling of custom tailwind classes in tailwind.config.js is not working.

Additional context

No response

Logs

Dominant language
TypeScript
Stars
1.9k
Forks
192
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nuxt-modules/tailwindcss

All issues in nuxt-modules/tailwindcss

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.