You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Tailwind tools/plugins (eg @tailwindcss/vite), the tailwindcss dependency should be instead a peer dependency.
From comment, some advantages of using peer dependencies:
avoid duplicate of installed dependencies (eg where tailwindcss@4.0.1 and @tailwindcss/vite@4.0.0 (that uses tailwindcss@4.0.0) are both dependencies and there are different behaviors at runtime) that:
can lead the singleton issues (multiple instances that can break the runtime execution)
reduces the size of the installed dependencies
control and flexibility using a specific version
Related informations, reasons and examples on PRs:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In the Tailwind tools/plugins (eg
@tailwindcss/vite
), thetailwindcss
dependency should be instead a peer dependency.From comment, some advantages of using peer dependencies:
tailwindcss@4.0.1
and@tailwindcss/vite@4.0.0
(that usestailwindcss@4.0.0
) are both dependencies and there are different behaviors at runtime) that:Related informations, reasons and examples on PRs:
If you agree, up this discussion and/or comment.
Beta Was this translation helpful? Give feedback.
All reactions