Open bennet-esyoil opened 2 years ago
This might be because tailvue has dark-mode classes added to its components .. maybe you have to turn dark mode on?
Which version of tailwind are you using?
Which version of tailwind are you using?
Currently in my package.json I have "@nuxtjs/tailwindcss": "^5.1.3",
This might be because tailvue has dark-mode classes added to its components .. maybe you have to turn dark mode on?
I do have darkmode turned on, I even have a toggle for that.
If I remove every occurence with ":dark" that's in the compiled file the project at least builds again - but theres still a big overlay that does not get the classes applied.
Did you import the module in correct order inside your nuxt.config.ts
?
modules: [
'@nuxtjs/tailwindcss',
'@tailvue/nuxt',
],
So you want to make sure the '@nuxtjs/tailwindcss'
is before '@tailvue/nuxt'
.
I put together a quick demo that converts to Tailwind from WindiCSS let me know if that is any help.
It sadly does not really.
I've created a very very very minmal repo here: https://github.com/bennet-esyoil/tailvue-nuxt3
To run, just npm ci
and npm run dev
and the build error appears. I'll be debugging this further but at the moment, I have no clue what's happening. In your main.css there's no @tailwind so maybe that has something to do with it. When I take it out I get no build errors, but am also loosing all styling
I think that class you are adding is conflicting with Tailwind
If I remove that then I see the following
tmp/testing/tailvue-nuxt3/assets/css/main.css:2:1: The ring-danger-light: class does not exist. If ring-danger-light: is a custom class, make sure it is defined within a @layer directive.
so I am not sure these are getting used properly
I see what you mean.
Autoformatter is breaking that for me. When I remove the whitespace it at least throws me another error.
So I guess my problem is not related to this lib at all, but somehow made the error first appear. I've been using it that way for at least a month now without any issues.
Feel free to close.
Yea I would check on those classes you are adding and make sure they are not conflicting with the base tailwind classes which is where I think the issue with the TailVue lib was it needed those dark class directives.
Not related but in it nuxt config you can just use modules instead of buildModules when using Nuxt 3 according to their docs.
Hey,
I'm getting the following error:
tailwind.config.js:
tailwind.css in assets has the following on line 71:
When I take out the
"node_modules/tailvue/dist/tailvue.es.js",
in the content section my project builds again.Any more information needed?