Skip to content

Pin the npm upgrade task to @tailwindcss/upgrade@4.1.4#544

Merged
flavorjones merged 1 commit intomainfrom
flavorjones/pin-upgrade-ci-to-4.1.4
May 2, 2025
Merged

Pin the npm upgrade task to @tailwindcss/upgrade@4.1.4#544
flavorjones merged 1 commit intomainfrom
flavorjones/pin-upgrade-ci-to-4.1.4

Conversation

@flavorjones
Copy link
Member

@flavorjones flavorjones commented May 2, 2025

We're pinning to v4.1.4 because v4.1.5 of the upgrade tool introduces a dependency version check on tailwind and I haven't been able to figure out how to get that to work reliably and I am extremely frustrated with the whole thing.

The error we're seeing in CI and in development with v4.1.5:

run npx @tailwindcss/upgrade --force --config /home/flavorjones/code/oss/tailwindcss-rails/My\ Workspace/test-upgrade/config/tailwind.config.js from "." ≈ tailwindcss v4.1.5 │ Searching for CSS files in the current directory and its subdirectories… Error: Tailwind CSS is not installed at k.factory (file:///home/flavorjones/.local/share/mise/installs/node/22.12.0/lib/node_modules/@tailwindcss/upgrade/dist/index.mjs:194:727) at k.get (file:///home/flavorjones/.local/share/mise/installs/node/22.12.0/lib/node_modules/@tailwindcss/upgrade/dist/index.mjs:4:6572) at da (file:///home/flavorjones/.local/share/mise/installs/node/22.12.0/lib/node_modules/@tailwindcss/upgrade/dist/index.mjs:194:820) at E (file:///home/flavorjones/.local/share/mise/installs/node/22.12.0/lib/node_modules/@tailwindcss/upgrade/dist/index.mjs:194:641) at xl (file:///home/flavorjones/.local/share/mise/installs/node/22.12.0/lib/node_modules/@tailwindcss/upgrade/dist/index.mjs:241:10846) 

At some point we will probably need to unpin this at which point I am sincerely hoping that someone else will figure out how to do it.

@flavorjones flavorjones changed the title ci: pin upgrade test to @tailwindcss/upgrade@4.1.4 Pin the npm upgrade task to @tailwindcss/upgrade@4.1.4 May 2, 2025
because the 4.1.5 upgrade tool introduced a dependency on tailwind that I can't figure out how to resolve. Gah, this entire experience has been entirely frustrating as a downstream maintainer, FML
@flavorjones flavorjones force-pushed the flavorjones/pin-upgrade-ci-to-4.1.4 branch from 0eeca37 to 9c71790 Compare May 2, 2025 20:29
@flavorjones flavorjones merged commit 2850839 into main May 2, 2025
17 checks passed
@flavorjones flavorjones deleted the flavorjones/pin-upgrade-ci-to-4.1.4 branch May 2, 2025 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant