-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
refactor(eslint-plugin): migrate to TS-ESLint infrastructure #7276
Conversation
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site settings. |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-7276--docusaurus-2.netlify.app/ |
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site settings. |
Size Change: 0 B Total Size: 806 kB ℹ️ View Unchanged
|
version "5.21.0" | ||
resolved "https://registry.yarnpkg.com/@typescript-eslint/utils/-/utils-5.21.0.tgz#51d7886a6f0575e23706e5548c7e87bce42d7c18" | ||
resolved "https://registry.npmmirror.com/@typescript-eslint/utils/-/utils-5.21.0.tgz#51d7886a6f0575e23706e5548c7e87bce42d7c18" |
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.
is this npmmirror change expected?
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.
Oh, thanks for noticing🤦♂️ I usually remember to revert the resolution before pushing, but forgot this time. It will be corrected next weekend when I bump dependencies.
It's mostly benign. npmmirror
is trustable.
If we migrate to Yarn v3 (#6028), the resolved registry URL will not be in the lockfile.
Pre-flight checklist
Motivation
Continuation of #7206. This is in the spirit of #5817. It's also hugely helpful because all AST information will now be strictly encoded in the types.
Test Plan
All unit tests still pass