What should we do in the new major

[G-Rath]

Just making this meta issue to consolidate what we'd like to land in/around the new major, since we've made some comments in different places:

• Drop Node 8 support (feat: drop support for node 8 #570)
• Update recommended ruleset (Update recommended ruleset #571)

Depending on time, we could try to do #482.

(I don't think we're in any major rush, since we're not actually blocking anything re jest 26 or eslint 7 - I could be wrong there?)

@SimenB made some comments too:

• Dropping eslint 5 support (👍)
• Use the suggestions api for things, such as:
  • toStrictEqual - personally I'm happy with that remaining an autofix, because running your tests should tell you if it's actually changed a behaviour (which is also why I wondered if maybe it should be recommended - it strikes me as a bit like == vs ===?)
  • no-test-callback should use a suggestion as it's dangerous to autofix
• Renaming no-test-callback to no-done-callback as it's a more accurate name (👍)

[SimenB]

And adding support for hooks (before{All,Each}, after{All,Each}) for that last one.

Nothing else comes to mind, @thymikee @jeysal ideas?

[jeysal]

My only ambition for a major would be the recommended ruleset update 🙃 (but as posted over there in the relevant issue, I'd prefer to add like a billion things to it so.... 😅 )

[G-Rath]

I've created #649 to track adding support for hooks - are we considering that a breaking feature?

Once I've done #649 I'll rename the rule to no-done-callback.

[SimenB]

https://github.com/jest-community/eslint-plugin-jest/releases/tag/v24.0.0