feat: add support for packageExtensions in yarn and pnpm#1847
Conversation
commit: |
packageExtensions in yarn and pnpm
webpro
left a comment
There was a problem hiding this comment.
Thanks for the PR! Much appreciated. A few comments I have.
| @@ -0,0 +1,16 @@ | |||
| export type PnpmConfig = { | |||
| pnpm?: { | |||
There was a problem hiding this comment.
I see why we are doing this, but any chance we could extend and use PackageJson?
There was a problem hiding this comment.
I refactored them in 269d602 (this PR), but I am not totally sure if you meant it that way. Let me know what you think 👍
|
The change of moving the |
|
Sorry forgot about that. If |
Thank you very much. That makes a lot of sense! |
|
Thank you! Nice work. |
|
🚀 This pull request is included in v6.25.0. See Release 6.25.0 for release notes. Using Knip in a commercial project? Please consider becoming a sponsor. |
Description
This PR adds support for the
packageExtensionssetting for yarn and pnpm (onlypeerDependencies). While at it, I also refactored some of the existing code (extracting types, addingenablersto pnpm, stuff like that) and also consolidate the tests and fixtures a little bit.packageExtensions#1779