Repository navigation
fix: stop false Tailwind sourcemap warnings - #134
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@tailwindcss/viteand@tailwindcss/postcssintegrations to the same fixed releaseWhy
@tailwindcss/vite@4.2.4returned the original source string for CSS files that were not Tailwind roots. Rollup therefore recorded a transform without a source map and emitted repeatedSOURCEMAP_BROKENwarnings. Tailwind fixed that contract violation in tailwindlabs/tailwindcss#20103 by returning no transform result for unchanged CSS; the fix shipped in 4.3.1.This change uses the current 4.3.3 patch release instead of filtering warnings. Legitimate sourcemap warnings from other plugins remain visible.
Validation
CI=true corepack pnpm install --frozen-lockfilecorepack pnpm --filter @codori/client lintcorepack pnpm --filter @codori/client typecheckcorepack pnpm --filter @codori/client test— 82 files and 533 tests passedcorepack pnpm --filter @codori/client build— succeeded with 0@tailwindcss/vite:generatewarningscorepack pnpm build— all workspace packages built with 0 Tailwind sourcemap warningsentry.*.csscontains Nuxt UI tokens and compiled Tailwind utilities, with no uncompiled@import "tailwindcss"main.cssVite module returned HTTP 200 without a Tailwind sourcemap warningKnown gap
The full Nuxt document route returned HTTP 500 in this tool PTY because the existing Nuxt 4.4.4 dev runtime reported
NUXT_VITE_NODE_OPTIONS.socketPath is not defined. That unrelated local-runtime failure reproduced before and after this dependency change; the Vite CSS transform itself was exercised directly and succeeded.Closes #132