-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
chore: remove support for browser
field in config
#9943
Conversation
3775116
to
d992628
Compare
d992628
to
bbe793b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Co-authored-by: Michał Pierzchała <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #9943 +/- ##
=======================================
Coverage 64.23% 64.23%
=======================================
Files 292 292
Lines 12466 12466
Branches 3075 3076 +1
=======================================
Hits 8007 8007
- Misses 3810 3811 +1
+ Partials 649 648 -1
Continue to review full report at Codecov.
|
@@ -12731,11 +12717,6 @@ resolve-url@^0.2.1: | |||
resolved "https://registry.yarnpkg.com/resolve-url/-/resolve-url-0.2.1.tgz#2c637fe77c893afd2a663fe21aa9080068e2052a" | |||
integrity sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo= | |||
|
|||
[email protected]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yesss!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, thank you!
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
This allows us to remove the dependency on
browser-resolve
. As the added deprecation message states, people can specify it asresolver
if they want to use it.Should make sure to specify the upgrade path in the blog post when we release Jest 26.
Test plan
Green CI? 😀 This removes a feature, so not much to test.