-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: bump @swc/core to 1.3.1 #5659
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
Conversation
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5659 +/- ##
==========================================
- Coverage 91.63% 91.01% -0.63%
==========================================
Files 134 365 +231
Lines 1506 11962 +10456
Branches 226 3483 +3257
==========================================
+ Hits 1380 10887 +9507
- Misses 62 781 +719
- Partials 64 294 +230
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
The yarn.lock additions pain me because there's nothing we can do yet... It this pr is good!
@JoshuaKGoldberg - we could stub all of those packages out if they aren't actually used by doing something like
it would at least reduce our install size and the install speed (as long as the packages aren't actually used) |
They fixed the regression they introduced which was preventing us from upgrading (swc-project/swc#4851), but it looks like a newer version changed how things worked, so we can no longer spy on an ES6 module's exports.
This PR just converts those spies to be fully mocked modules to work around this and allow us to upgrade