-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
feat!: drop support for jiti < 2.2.0 #20016
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
✅ Deploy Preview for docs-eslint canceled.
|
|
The CI failure seems unrelated. |
Indeed. It appears this is failing in all the workflow runs now. (e.g. https://github.com/eslint/eslint/actions/runs/17082032100) |
The failure should have been fixed in 6c07420. |
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.
LGTM, thanks! It could take some time until this is merged because the preparations for ESLint v10 aren't quite done yet. Since this is a feature, it will also need another review.
|
Sounds good! Should I just leave it in draft until then? |
Yes, we will undraft this after retargeting to a v10.x branch. |
|
@michaelfaith can you please fix merge conflicts, and also update the v10 migration guide in this PR? https://github.com/eslint/eslint/blob/main/docs/src/use/migrate-to-10.0.0.md We plan to include this change in ESLint v10.0.0-alpha.0, which is scheduled for November 14th. |
|
Note: the PR should still target the |
|
Sure thing. I'll take care of it this weekend. |
This change removes support for `jiti` `< 2.2.0`. Now, if you're wanting to use a TypeScript config without Node's native type stripping, you must have at least version `2.2.0` of `jiti` installed.
0bf4275 to
6905d9c
Compare
|
@mdjermanovic I've rebased and resolved the conflicts. Also, added a section to the migration doc. Let me know what you think. |
|
I've marked the PR as ready for review. |
correct latest jiti version Co-authored-by: Francesco Trotta <[email protected]>
mdjermanovic
left a comment
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.
LGTM, thanks! Leaving open for @fasttime to verify.
fasttime
left a comment
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.
LGTM, thanks!
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
What changes did you make? (Give an overview)
This change removes support for
jiti< 2.2.0. Now, if you're wanting to use a TypeScript config without Node's native type stripping, you must have at least version2.2.0ofjitiinstalled.Fixes #19765