-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: enable unicorn/prefer-node-protocol
#9742
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: enable unicorn/prefer-node-protocol
#9742
Conversation
Thanks for the PR, @abrahamguo! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 525e1ac. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
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.
YES
Since CI is now green on Let me know if anyone has any ideas off the top of their head. At a glance, I do not see how the CI failures could be related to this change, so I'll have to do a deep dive when I get a chance. |
525e1ac
382e87b
into
typescript-eslint:main
PR Checklist
eslint-plugin-unicorn
rules internally #9623Overview
Enable
unicorn/prefer-node-protocol
(docs). 100% autofixable.