Skip to content

@tailwindcss/upgrade ignores pnpm catalogs #17879

Closed
@MartinCura

Description

@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",

Image

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions