-
Notifications
You must be signed in to change notification settings - Fork 374
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
[Bug?]: SolidStart fails to start with Daisyui and tailwindcss #1503
Comments
Problem looks to be originating from useAssets(() => (assets.length ? assets.map(m => renderAsset(m)) : undefined)); |
Lol, I think there is a problem with the template, I just went through the manual process of adding tailwind in the basic template and It worked. |
I‘m alos having this issue, but I did not use any ui framework... |
did your issue also solve itself once you did the manual setup? |
nope, it's still here |
can you share how you did the setup? |
Same here, but without even adding DaisyUI.
|
Same error here, except I'm not using DaisyUI. Just started a new solid-start project with tailwindcss (using javascript). I added a useAssets(() => (assets?.length ? assets.map(m => renderAsset(m)) : undefined)); That fixed the issue, but not sure of the implications of that. |
Same here. I didn't used tailwindcss and I used solid-styled-components.
And, @eduludi 's fix is worked well. However, this is just temporary fix. |
I've fixed this issue through a very strange way. I add useAssets(() => (assets?.length ? assets.map(m => renderAsset(m)) : undefined)); That fixed this issue temporarily, but there is a Hydration Mismatch error shows up after the app started. I checked the entire project and found out nothing unnormal, so I tried adding a After this I delete the |
@harveylii Is it to any good for you to make a pr, I fixed by doing the work of setting up tailwindcss with daisyui manually in the basic template. So It makes me think that there is a problem with the template itself, and not with the framework. But probably I'm wrong as I'm not very familiar with the internal workings of solid start |
I think my last PR already implemented the equivalent of that fix, since I just gave |
@Brendonovich so, it's just a matter of updating the templates and the dependencies? |
Once the change is released yeah |
sounds good |
I got the same problem here. I just started a new solid start project with tailwind CSS (the starter). It presented the error on the first Building it and then running with |
v1.0.1 seems to fix the issue for me. 🎉 |
Yes! Can confirm it's been fixed. |
Can confirm, v1.0.1 fixed the issue |
Duplicates
Latest version
Current behavior 😯
After installing daisyui following their documentation and adding it to tailwindcss, the server fails to build the client and I can't start the dev server.
here is the output
However the build process works and the nitro server doesn't fail
Expected behavior 🤔
Start the dev server without errors
Steps to reproduce 🕹
Steps:
when a command is [cmd1|cmd2] means I rand both of then to test.
[pnpm|npm] create solid
and check the tailwindcss option[bun|pnpm|yarn] install daisyui@latest
[bun|pnpm] dev
, then, open the browser, the output in the terminal should be:Context 🔦
I'm trying to make a website with tailwindcss, daisyui to be deployed to cloudflare workers
Your environment 🌎
The text was updated successfully, but these errors were encountered: