-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support pnpm Catalogs #30079
Comments
is there anyone working on this? |
Not yet, so go ahead |
I'm afraid I'm not available until after Christmas, please don't assign me till I confirm, thank you |
Nobody else will be working on it before then so that's ok. Thanks! |
Chiming in that if @faradaytrs has not started on this, or if you are not sure about your availability, that I would be happy to work on this instead! I sketched out a few approaches a while back, and I have time over the next month to poke at it ✍️ Aside: I will have some open questions about the implementation. For example, since catalogs are managed in |
The npm manager in renovate can return additional package files so I think it's probably best to handle it in the existing manager |
sure, please go ahead |
We will be moving out yarn and pnpm from the npm module someday so it aligns with that refactor too I think. |
Describe the proposed change(s).
Pnpm v9.51 introduced a new way to share dependencies inside workspaces, they call it catalogs2.
This is related to #25335.
Footnotes
https://github.com/pnpm/pnpm/releases/tag/v9.5.0 ↩
https://pnpm.io/catalogs ↩
The text was updated successfully, but these errors were encountered: