DioxusLabs / DioxusLabs/dioxus

Dioxus 0.7-rc.1 Tailwind inclusion doesn't include plugins (DaisyUI)

Open
#4,786 5 comments 2 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
39.1k
Forks
1.9k
Avg merge
4d 10h
Merged PRs (30d)
4

Description

**Problem**

In the migration from 0.6 to 0.7-rc.1, I noticed that the current method of including plugins from `input.css` does not work anymore. Tailwind CSS classes and adaptations are rendered, but DaisyUI-specific styles are not.

https://daisyui.com/docs/install/dioxus/ refers to the inclusion via `tailwind.css` and not `input.css`, but no noteable difference is observed. The `dx serve` Tailwind runner just copies the `@plugin` directives without expanding them.

**Steps To Reproduce**

Steps to reproduce the behavior:

- Include DaisyUI as plugin (per https://daisyui.com/docs/install/ ) in `input.css`
- Run `dx serve --web` with `dioxus-cli` (v. 0.7-rc.1)

**Expected behavior**

The manual watcher used in 0.6 was `npx @tailwindcss/cli -i ./input.css -o ./assets/tailwind.css --watch`, which correctly included the plugin. Either enable the built-in watcher to recognize plugins or allow to use the dedicated Tailwind watcher for non-standard configurations.

Rendering via Tailwind CLI to a separate CSS file (e.g. `main.css`) does work, but separates the workflow and creates duplicate Tailwind classes when also including the Dioxus file.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.