[MAJOR] v8 planning #8766
Replies: 15 comments 20 replies
-
|
#8554 - [rule-tester] support multipass fixes |
Beta Was this translation helpful? Give feedback.
-
|
This change will be invisible for linting users and should only cause minimal disruption for rule authors. |
Beta Was this translation helpful? Give feedback.
-
|
#8347 - Enhancement: Differentiate AST node types without parent (for estree) and with parent (for eslint) |
Beta Was this translation helpful? Give feedback.
-
|
This change will be invisible for linting users. It will only impact programmatic consumers of |
Beta Was this translation helpful? Give feedback.
-
|
#8243 - Configs: [prefer-nullish-coalescing] change default for |
Beta Was this translation helpful? Give feedback.
-
|
TODO: @JoshuaKGoldberg and I still need to resolve this issue and decide if we agree on this change. |
Beta Was this translation helpful? Give feedback.
-
|
If we do go for it, I think it's a small enough change that we can lump it into v8. It makes the rule less strict by default. Not very user-action-needing. |
Beta Was this translation helpful? Give feedback.
-
|
#8113 - [no-invalid-void-type]: refactor to use type checking |
Beta Was this translation helpful? Give feedback.
-
|
This change will be a pretty major piece of work as we essentially need to rewrite the rule. Given we have a number of other rule changes slated for this release (eg deleting all formatting rules) it might be better to bump this to make it easier for us to action this major and for users to migrate. Proposal: bump to v9 |
Beta Was this translation helpful? Give feedback.
-
|
I'm in favor. Agreed both that this change is a good one and it's got big user impact. Given that the rule is only in |
Beta Was this translation helpful? Give feedback.
-
|
#8092 - deprecate |
Beta Was this translation helpful? Give feedback.
-
|
This will have high user impact as Proposal: keep for v8 |
Beta Was this translation helpful? Give feedback.
-
|
#8074 - 💀 Rule deletions: formatting rules |
Beta Was this translation helpful? Give feedback.
-
|
Very high user impact but migration should be pretty mechanical over to Resolution: keep for v8 |
Beta Was this translation helpful? Give feedback.
-
|
#6433 - AST cleanup: type parameter in |
Beta Was this translation helpful? Give feedback.
-
|
This is going to be a really large breaking change that will be painful for users to deal with. Proposal:
|
Beta Was this translation helpful? Give feedback.
-
|
Saving the 'breaking' part of this and #1305 for v9 feels like a repeat of our v7 strategy for dropping older backwards compatibility support. Which I like. It feels like we're moving towards alternating which majors are "big" (evens) vs. more for bumping minimum versions (odds). |
Beta Was this translation helpful? Give feedback.
-
|
#6403 - Error if configuration options aren't provided as expected |
Beta Was this translation helpful? Give feedback.
-
|
This is user-visible but should be very, very low impact as current misuse of options should be rare. Any errors revealed would show users problems with their config - which is a good thing. Proposal: keep for v8 |
Beta Was this translation helpful? Give feedback.
-
|
#5856 - Remove |
Beta Was this translation helpful? Give feedback.
-
|
My preference would be to keep for v8. Per #5856 (comment), I can't think of a reason that someone would want this now. |
Beta Was this translation helpful? Give feedback.
-
|
#5855 - Investigate removing |
Beta Was this translation helpful? Give feedback.
-
|
My preference would be to keep for v8. Especially with the new project service settings, we really don't want people relying on isolated programs. |
Beta Was this translation helpful? Give feedback.
-
|
#1305 - Align AST for |
Beta Was this translation helpful? Give feedback.
-
|
This is going to be a really large breaking change that will be painful for users to deal with. Proposal:
|
Beta Was this translation helpful? Give feedback.
-
I think this is good idea. It's also really hard to keep track of all the new rules that some minor versions introduce. I have had to update typescript-eslint that was lagging almost year behind it was impossible to read the changelog because there were so many versions 😅 Though, it was not a problem that I did not read it the changelog because there was no breaking changes :) What I'm mostly thinking is, that it's nice to kinda get new major version that offers you new enabled lint rules, so you can get easily benefit from them. |
Beta Was this translation helpful? Give feedback.
-
|
When will it be possible to use typescript-eslint with eslint 9, without needing a beta version? |
Beta Was this translation helpful? Give feedback.
-
|
https://typescript-eslint.io/blog/announcing-typescript-eslint-v8-beta |
Beta Was this translation helpful? Give feedback.
-
|
Now that all the requisites for Eslint v9 are met, what will happen? |
Beta Was this translation helpful? Give feedback.
-
|
We're planning on releasing on Wednesday July 31st. 🚀 |
Beta Was this translation helpful? Give feedback.
-
|
Hurry up — they already made version 10 😄
|
Beta Was this translation helpful? Give feedback.
-
|
Uh oh! @RobinTail, the image you shared is missing helpful alt text. Check #8766 (reply in thread). Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.
|
Beta Was this translation helpful? Give feedback.
-
|
Can somebody write a clear migration guide from the "legacy" typescript-eslint setup to new typescript-eslint setup? Since I think I also need to remove Then I need to install It's quite confusing for me, and most likely for others. It's not just a migration from the old config to the new flat config file, it's not just eslint 7/8 to eslint 9. But it's also how to migrate from the typescript-eslint legacy setup to the new recommended setup. It would be nice if a migration guide could be added to either: https://typescript-eslint.io/getting-started/ or https://typescript-eslint.io/getting-started/legacy-eslint-setup. Thank you in advance for thinking along with me. |
Beta Was this translation helpful? Give feedback.
-
Note - it's not our setup, it's eslint's new flat config system. Including their config migration guide which includes information about how to use their config migration tool. |
Beta Was this translation helpful? Give feedback.
-
|
I'm specifically talking about typescript-eslint. Namely https://typescript-eslint.io/getting-started/legacy-eslint-setup vs https://typescript-eslint.io/getting-started/. I do think it's part of this project setup. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Timeline
(updated July 25th, 2024): we plan on releasing typescript-eslint@v8 as stable on July 31st, 2024. This will include full ESLint v9 support and a stabilize
parserOptions.projectService. You can read more on https://typescript-eslint.io/blog/announcing-typescript-eslint-v8-beta. 🎉Milestone: https://github.com/typescript-eslint/typescript-eslint/milestone/9
Breaking changes: https://github.com/typescript-eslint/typescript-eslint/issues?q=is%3Aissue+label%3A%22breaking+change%22+milestone%3A8.0.0
Background
Discussing internally off the back of my tweet thread we're thinking about trying some smaller major releases this year.
Historically our major releases have always been quite large and unwieldy for users. We often rework many rules, change the AST, delete rules, remove options, and change the recommended configs. It's a lot for a user to read, understand and action and we have a hypothesis that this fuels fragmentation amongst our userbase.
On top of that these large releases are a massive piece of work for us to prepare - often taking months of work to prepare and build along with the constant pain of syncing the ongoing minor releases.
Our latest major release (v7) was a very small major - it just bumped minimum dependency requirements. This release is only a few weeks old and yet ~14% of the userbase has already migrated - which seems to support the above hypothesis as upgrading to v7 did not require much reading or effort from users.
typescript-eslint Version 8
For this major we're currently discussing which breaking changes make the cut.
Stay tuned as we update this post with relevant discussions.
Beta Was this translation helpful? Give feedback.
All reactions