nuxt-modules / nuxt-modules/tailwindcss
The version of Tailwind on GitHub differs from the version published on npm
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 192
- PR merge metrics
- No merged PRs in 30d
Description
Environment
| Operating system | Windows 10.0.22631 |
| CPU | 12th Gen Intel(R) Core(TM) i7-12700H (20 cores) |
| Node.js version | v24.4.0 |
| nuxt/cli version | 3.33.1 |
| Package manager | pnpm@10.30.0 |
| Nuxt version | 4.3.1 |
| Nitro version | 2.13.1 |
| Builder | vite@0.10.3 |
| Config | compatibilityDate, devtools, modules, routeRules |
| Modules | @nuxtjs/tailwindcss@6.14.0 |
Reproduction
No response
Describe the bug
The Tailwind version on GitHub is 4.1.12, whereas the version on npm is ~3.4.17
Additional context
No response
Logs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the repository's GitHub version (4.1.12) with the npm version (~3.4.17) reported for @nuxtjs/tailwindcss@6.14.0; verify which package and release each version refers to. Done means the published npm package and GitHub version are aligned or the discrepancy is explained using the module's package metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, tailwindcss, typescript
- Domain
- frontend, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100