-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bun] WARN - "As of Tailwind CSS v3.0, trueGray has been renamed to neutral" etc #809
Comments
I think the answer might be obvious, since we do not have many options: a problem with the handling of weak/strong references, or more generally Bun's garbage collector implementation. I don't know how to express this directly to Bun maintainers. |
Sorry, i don't know much about the implementations and so on, that's why i asked. |
After reading the other issue i remembered that i tried to use delete as explained in tailwindlabs/tailwindcss#4690 (comment) but it did not change anything, so it really seems to be |
Any fixes for this, since NuxtUI automatically imports tailwind? |
You have to track it under oven-sh/bun#6747, fixes for this have to be implemented in Bun |
A workaround to get rid of it: // https://github.com/nuxt/ui/issues/809
import { createRequire } from 'node:module'
const _require = createRequire(import.meta.url)
const defaultColors = _require('tailwindcss/colors.js')
delete defaultColors.lightBlue
delete defaultColors.warmGray
delete defaultColors.trueGray
delete defaultColors.coolGray
delete defaultColors.blueGray (you can put it in /cc @benjamincanac it is also doable within module but sadly I could not setup a dev env for |
@pi0 Thanks a lot for the fix! 😊 |
@thunfisch987 @pi0 @benjamincanac If you remove the ...colors from theme.extend.colors, it works properly. |
Environment
Version
v2.9.0
Reproduction
Reproduction not possible because stackbiltz does not use bun
Description
This is not a breaking bug, but i'm curious why this only happens when using Bun, because it works perfectly fine except for this.
This does not happen when only using @nuxtjs/tailwindcss.
When i run the development server with
bun run dev
everything works as normal (because it uses node to run it), but when i usebun run --bun dev
errors likesee also: tailwindlabs/tailwindcss#4690
Additional context
Logs
The text was updated successfully, but these errors were encountered: