Setting tailwindcss version in the Trunk config file does not update Tailwind CLI

[Stephen Power]

Setting a new Tailwind version via the config file Trunk.toml does not update the Tailwind CLI version.

Here's my config file before adding Tailwind:

[build]
release = true
dist = "dist"
public_url = "/"
filehash = true

[watch]
watch = []
ignore = []

[serve]
address = "127.0.0.1"
port = 42069
open = false
no_autoreload = false

[clean]
dist = "dist"
cargo = false

[tools]
sass = "1.54.9"
wasm_bindgen = "0.2.88"
wasm_opt = "version_116"

If I include a new Tailwind feature, it gives errors. For example, adding a new Tailwind class does not work.

@layer utilities {
    .mobile-page {
        @apply h-dvh;
    }
}

Running trunk serve with the above Tailwind utility class, gives the following error: The 'h-dvh' class does not exist.

Adding Tailwind to my Trunk.toml file does not fix the issue:

[tools]
sass = "1.54.9"
wasm_bindgen = "0.2.88"
wasm_opt = "version_116"
tailwindcss = "3.4.1"

Running trunk serve gives the aforementioned error.

Note: This Tailwind version definitely has the h-dvh class.

However, updating the wasm-bindgen version causes Tailwind to also update:

[tools]
sass = "1.54.9"
wasm_bindgen = "0.2.90"
wasm_opt = "version_116"
tailwindcss = "3.4.1"

Running trunk serve now works and does not give any Tailwind class errors.

[Jens Reimann]

This looks indeed like a bug. I think that should be fixed by PR #687 … it would be great if you could try that out.