fix(bundle-source): Relieve execa dependency #2164
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gibson042
approved these changes
Mar 21, 2024
kriskowal
force-pushed
the
kriskowal-bundle-source-execa
branch
from
5f536f1
to
5fc08ca
Compare
kriskowal
force-pushed
the
kriskowal-bundle-source-execa
branch
from
5fc08ca
to
eff91d8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bundle Source 3.1.0 introduced a postinstall dependency on patch-package that is not likely to exist for most users and not retained as a dependency. The patch is necessary because execa retains onetime retains mimic-fn with a SES incompatibility. That has since been fixed, but until that rolls up into the dependent packages, execa is an unnecessary liability for bundle source tests.