Skip to content

Conversation

@zkochan
Copy link
Contributor

@zkochan zkochan commented May 5, 2022

What's the problem this PR addresses?

The packageExtensions compat database is useful for pnpm as well.
By moving it to a separate package, we can use it in pnpm and
recommend the pnpm users to extend the database as well.

How did you fix it?

...

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

The packageExtensions compat database is useful for pnpm as well.
By moving it to a separate package, we can use it in pnpm and
recommend the pnpm users to extend the database as well.
zkochan added a commit to pnpm/pnpm that referenced this pull request May 5, 2022
zkochan added a commit to pnpm/pnpm that referenced this pull request May 6, 2022
zkochan added a commit to pnpm/pnpm that referenced this pull request May 7, 2022
@arcanis arcanis merged commit 9bd61fb into yarnpkg:master May 8, 2022
@merceyz
Copy link
Member

merceyz commented May 9, 2022

@zkochan The new package has been published 👍

merceyz added a commit that referenced this pull request Jul 20, 2022
* feat: move compat database to separate package

The packageExtensions compat database is useful for pnpm as well.
By moving it to a separate package, we can use it in pnpm and
recommend the pnpm users to extend the database as well.

* Renames packages/extensions -> packages/yarnpkg-extensions

* Fixes constraints

* refactor: re-use extensions

* chore: remove unnecessary test

* chore: start at `1.0.0`

Co-authored-by: Maël Nison <[email protected]>
Co-authored-by: merceyz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants