Clojurians Log v2
biff
Just running through the tutorial and I am running into some sort of problem with the tailwindcss not being applied. I don't see it rebuilding after being downloaded and I get an "Error: cannot apply unknown utility class mb-3 (along with others if I comment out that particular class), this comes along with a stack trace(this is just part of it): {:proc #object[java.lang.ProcessImpl 0xf4767e1 "Process[pid=191159, exitValue=1]"], :exit 1, :in #object[java.lang.ProcessBuilder$NullOutputStream 0x32d689b0 "java.lang.ProcessBuilder$NullOutputStream@32d689b0"], :out #object[java.lang.ProcessBuilder$NullInputStream 0x6ba6d9a2 "java.lang.ProcessBuilder$NullInputStream@6ba6d9a2"], :err #object[java.lang.ProcessBuilder$NullInputStream 0x6ba6d9a2 "java.lang.ProcessBuilder$NullInputStream@6ba6d9a2"], :prev nil, :cmd ["bin/tailwindcss" "-c" "resources/tailwind.config.js" "-i" "resources/tailwind.css" "-o" "target/resources/public/css/main.css" "--watch"], :type :babashka.process/error} Has anyone encountered this before? Thanks.
I'm getting the same error. I bet this is something to do with tailwind 4 being released recently, since the taliwind downloader thing takes the most recent version. still investigating.
I've fixed/worked around this issue by setting an explicit version of the tailwind binary to install, with a default of 3.4.17 (since v4.0.0 evidently has breaking changes). To upgrade an existing project:
1. Put :biff.tasks/tailwind-version "v3.4.17" in resources/config.edn
2. Update your :dev alias biff version to {:deps/root "libs/tasks", :git/sha "1ade0c3", :git/tag "v1.8.28", ...}
3. Run rm bin/tailwindcss; clj -M:dev install-tailwind
Alright great thanks very much Jacob.
Theres an upgrade script available that seemlessly upgrades tailwind versions that they provide: npx @tailwindcss/upgrade@next That could likely be adapted to work with Biff.
we had the opposite problem here: biff was installing the latest version but we wanted to pin/downgrade to an old version.
interesting, haven't seen that before. I'll see if I can reproduce it tomorrow.
Thanks, would the rest of the stack trace be useful to you?
I don't think so, looks like it's just saying it shelled out to tailwind which then had an error. I'll probably have other questions though!