Support ESLint v9 (including Flat Config)

[dangreenisrael]

Support ESLint v9 (including Flat Config)

[G-Rath]

Core maintainer of eslint-plugin-jest here 👋

I personally really like this plugin and want to make sure it's well supported - it doesn't look like there's been activity though in 2 years.

I technically don't have the authority to do this but I'm pretty sure @SimenB wouldn't object to having ownership of this plugin transferred to @jest-community to sit alongside eslint-plugin-jest and allow myself and others to help with the maintenance if that's something @dangreenisrael would be interested in.

Personally I'm also happy to have these rules live directly in eslint-plugin-jest though there might be a strong technical reason for why that shouldn't happen.

I'm also happy to help with the ESLint v9 support - @jamiehaywood let me know if you're still interested in doing that, have questions, etc; otherwise I can also pick it up if you're too busy.

[dangreenisrael]

I'm alive 🎉. I've heads down at a new job for the last few monhts.

[hockeybuggy]

I know you work/worked with Dan. Do you know his status?

Alive but a father of young children (child?) so I think his availability has been (reasonably) limited. I'll try to track him down so we can figure out publishing and ownership/maintenance.

Feel free to tag me for a second reviewer. I am glad that people have found some utility here.

[jamiehaywood]

so the workaround config for ESLint 9 is to create an object in your flat config:

import jestFormatting from 'eslint-plugin-jest-formatting'

export default [
...
  {
    files: jestFormatting.configs.recommended.overrides[0].files,
    rules: jestFormatting.configs.recommended.overrides[0].rules,
    plugins: {
      "jest-formatting": jestFormatting,
    },
  }
]

[jamiehaywood]

hi @G-Rath! thanks for tagging me. Would be keen to raise a PR add ESLint 9 support - couple of questions:

1. Would v9 support PR come before or after migration into eslint-plugin-jest?
2. Has there been a reconsideration of this comment by @SimenB a couple of years ago? As I believe this is the reason that eslint-plugin-jest-formatting became its own plugin in the first place.

[benkimpel]

I'm not sure of @dangreenisrael's status, but I can merge PRs if I have another reviewer approval. What I can't do is a release to npm.

@hockeybuggy or @ryanwilsonperkin I know you work/worked with Dan. Do you know his status?

@G-Rath @jamiehaywood I'd be happy to review and merge if you want to take a chance that it might not make it to npm. We can do this while the ownership/maintenance discussions play out.

[dangreenisrael]

If @benkimpel can merge it, I can get it onto NPM.

[jamiehaywood]

I'm thinking a good example for supporting flat config is eslint-plugin-jest.

They have a createFlatConfig and add a flat/ appendix to the exports containing flat config.

I'll raise a draft PR over the next couple of weeks to sketch out backward compatible flat config support

[benkimpel]

Alive

Phew! Glad to hear it.

[dangreenisrael]

Has there been a reconsideration of jest-community/eslint-plugin-jest#17 (comment) by @SimenB a couple of years ago? As I believe this is the reason that eslint-plugin-jest-formatting became its own plugin in the first place.

I haven't heard anything from him.

[G-Rath]

@dangreenisrael glad to hear you're alive, and congrats (I hope 😄) on the new job!

Would v9 support PR come before or after migration into eslint-plugin-jest?

The order of operations shouldn't matter, so I say go for it.

I haven't heard anything from him.

I'll see if I can grab @SimenB for a chat, though it might take awhile so I would continue as you were in the meantime.

fwiw if this plugin does move the community, it would be ideal to switch to using GitHub Actions for CI (so that its one less SaaS to manage) and to use semantic-release for automatically releasing (so we don't need direct access to the package on npm) - both are things we use in the other eslint plugins and that I'd be happy to help setup if you're happy to switch to them now.

[benkimpel]

fwiw if this plugin does move the community, it would be ideal to switch to using GitHub Actions for CI (so that its one less SaaS to manage) and to use semantic-release for automatically releasing (so we don't need direct access to the package on npm) - both are things we use in the other eslint plugins and that I'd be happy to help setup if you're happy to switch to them now.

I think that'd be fine as it would make it easier for contributors to other eslint packages to be more comfortable in this one, whether it moves into the community or not.