@tailwindcss/upgrade ignores pnpm catalogs

[MartinCura]

What version of Tailwind CSS are you using?

v4.1.5 / insiders

What build tool (or framework if it abstracts the build tool) are you using?

Doesn't matter, but Next.js

What version of Node.js are you using?

v22.14.0

What browser are you using?

N/A

What operating system are you using?

Fedora

Reproduction URL

Sorry 😬 if really necessary i can make one up, but this is just a heads up of a minor issue.

Describe your issue

Hi all! I'd consider this quite minor, but taking the liberty to mention it: i ran

pnpm dlx @tailwindcss/upgrade@insiders --force

to try out #17831 (comment) and realized the upgrade tool doesn't seem to take into account pnpm's catalog syntax for specifying package versions? https://pnpm.io/catalogs With this approach dependency versions are actually found in pnpm-workspace.yaml. This is the abbreviated diff for my package.json:

-    "@tailwindcss/postcss": "catalog:",
-    "tailwindcss": "catalog:",
+    "@tailwindcss/postcss": "^4.1.5",
+    "tailwindcss": "^4.1.5",

Again, quite a nit and i'm sure not many people are using this just yet (though i like it for monorepos), but mentioning it in case it's useful. Low priority of course.

[philipp-spiess]

Hey! Thanks, agree that this could be better but realistically we won't get to that soon. I'm going to move this into the feature ideas section but we're happy to review a contribution if you want to take a look at this yourself 👍

[MartinCura]

I agree, and unless the upgrade tool becomes more powerful (such as being used for all minor/patch updates too) i don't think this is too important. Have a nice day.

[RobinMalfait]

As a small followup, the upgrade tool will be able to run on existing v4 projects starting at the next release.

However, we bump dependencies by calling your package manager (right now we support npm, yarn, bun and pnpm).

However, for catalogs, this seems to be a feature that pnpm might have in the future, but right now it's a manual process: https://pnpm.io/catalogs#caveats

[MartinCura]

that seems right to me: pnpm doesn't seem to fully use them yet, so if you're using the pm directly then this shouldn't be an issue when they cover the feature gap.