-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: fix failing integration tests on the main
branch
#10870
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: fix failing integration tests on the main
branch
#10870
Conversation
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
main
branchmain
branch
View your CI Pipeline Execution ↗ for commit 9d8e69e.
☁️ Nx Cloud last updated this comment at |
Thanks for the PR, @ronami! 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. |
main
branchmain
branch
main
branchmain
branch
Thanks @ronami! |
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.
🤕
Probably a good idea, yeah. Even if it's correct as-is, it's good to have SEO friendly questions about it. |
67ab379
into
typescript-eslint:main
PR Checklist
Overview
The
main
branch's integration tests are failing consistently. I think this is related to a recent release of@types/eslint__js
.The package itself seems to be deprecated and isn't necessary anymore, see:
@eslint/js
package eslint/eslint#19010I'm not sure why exactly, but it seems that the version currently released for
@types/eslint__js
as thelatest
tag has noindex.d.ts
file. I think this is causing the integration tests (that check that types are valid) to fail with:Cannot find type definition file for 'eslint__js'.
(even if the file checked is empty).Installing the
latest
version of@types/eslint__js
and type checking an empty file seems to error on the above.Should I open an issue about this? Having an empty
index.d.ts
can help in cases it's accidentally installed (unless this is intended since it's now deprecated).