fix(styles): resolve daisyUI 5 + Tailwind 3 conflict that crashes CSS#219
Open
evan188199-tech wants to merge 1 commit into
Open
fix(styles): resolve daisyUI 5 + Tailwind 3 conflict that crashes CSS#219evan188199-tech wants to merge 1 commit into
evan188199-tech wants to merge 1 commit into
Conversation
daisyUI was bumped to v5 (which targets Tailwind v4) while the project
stayed on Tailwind v3. Loading daisyUI 5 via the v3 `require("daisyui")`
pattern returns a v4 options-function instead of a v3 plugin object,
raising `TypeError: adapterFn is not a function` on every CSS compile.
Next.js then retries the failed compile by spawning worker processes,
which can fork-bomb the machine.
Take the minimal path (Option B from Snouzy#215): downgrade daisyUI to v4.x
(the last line compatible with Tailwind v3) and remove the no-op v4
`@plugin "daisyui"` directive from globals.css. Tailwind v3 and
`tailwind.config.ts` keep loading daisyUI via `plugins: [require("daisyui")]`.
Fixes Snouzy#215
|
Someone is attempting to deploy a commit to the Workoutcool Team Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
此 PR 由 GLM-5.2 修复。 |
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
1 participant
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.
What
pnpm dev/next buildcrashes on every page withTypeError: adapterFn is not a function, and Next.js's retry loop can fork-bomb the machine (1000+ node processes, multi-GB memory).Why
This is an incomplete Tailwind v4 migration. The CSS was updated to use
@plugin \"daisyui\"(v4 syntax) but the dependencies and config were left on v3. daisyUI was bumped to v5 — which dropped Tailwind v3 support — whiletailwindcssstayed at^3.4.13. Loading daisyUI 5 via the v3require(\"daisyui\")pattern returns a v4 options-function instead of a v3 plugin object.Changes
Take the minimal path (Option B from #215) instead of a full v4 migration:
daisyui→^4.12.10(v4 line, last version compatible with Tailwind v3). Lockfile resolved to4.12.24.@plugin \"daisyui\"directive fromglobals.css— it has no effect under Tailwind v3 anyway.tailwind.config.tsalready loads daisyUI viaplugins: [require(\"daisyui\")], so no config change is needed.pnpm-lock.yamlupdated viapnpm install --lockfile-only.This keeps the change small and reviewable. An alternative full Tailwind v4 migration exists in #216 if the maintainer prefers that direction instead.
Fixes #215.