Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

@tailwindcss/upgrade ignores pnpm catalogs #17879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MartinCura opened this issue May 5, 2025 · 0 comments
Closed

@tailwindcss/upgrade ignores pnpm catalogs #17879

MartinCura opened this issue May 5, 2025 · 0 comments

Comments

@MartinCura
Copy link

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.

@tailwindlabs tailwindlabs locked and limited conversation to collaborators May 6, 2025
@philipp-spiess philipp-spiess converted this issue into discussion #17897 May 6, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant