Version 6
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- nuxtjs, tailwindcss, vite
- Domain
- build-system, frontend
Research direction
Start by reproducing the reported setup with Nuxt version 6, Tailwind CSS 4.2, and @nuxtjs/tailwindcss 7.0.0-beta.1, then inspect the integration around the @tailwindcss/vite:generate:build warning. Done means the supported configuration is documented or fixed so the build completes without the reported warning.
Written by the indexing model from the issue text.
Description
Environment
This verison 6 , not support taildwindcss verison 4.
I try use version beta "@nuxtjs/tailwindcss": "7.0.0-beta.1",, support taildwindcss verison 4 but error
Reproduction
No response
Describe the bug
This verison 6 , not support taildwindcss laster verison 4.2
I try use version beta "@nuxtjs/tailwindcss": "7.0.0-beta.1",, but error warn
#14 18.95 WARN [plugin @tailwindcss/vite:generate:build] Sourcemap is likely to be incorrect: a plugin (@tailwindcss/vite:generate:build) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help (x21)
How to fix this error, when update version stable nuxtjs verison 7 , thanks begin
Additional context
No response
Logs
#14 18.95 WARN [plugin @tailwindcss/vite:generate:build] Sourcemap is likely to be incorrect: a plugin (@tailwindcss/vite:generate:build) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help (x21)
- 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
- 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.
More from nuxt-modules/tailwindcss
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nuxt-modules/tailwindcss#1039 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nuxt-modules/tailwindcss#1034 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nuxt-modules/tailwindcss#1033 · 1 comment ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 30/100
nuxt-modules/tailwindcss#1031 · 7 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nuxt-modules/tailwindcss#1003 · 10 comments · 1 reaction ·
All issues in nuxt-modules/tailwindcss
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·