Release the ESLint 8 version

[voxpelli]

It's been requested in: #69

See also: standard/eslint-config-standard#229

[framerate]

Please!

[fnwbr]

At medienhaus/ we've started using the workaround to specify a git commit hash as the version for the npm package. Since the issue was basically fixed on the master branch and we're all just waiting for the release on npm for it, this will solve the problem (and potential issues with npm install) in the meantime:
medienhaus/medienhaus-cms@9f00f9c

[derekhubbard]

Any update on this? Until this is fixed, I don't see a clean path forward to us using the latest version of node and npm due to invalid peer dependency checks.

[voxpelli]

I'm a bit choked right now, but I will have some discussions on this subject tomorrow, I may come back after that and see

[voxpelli]

Also, you probably want to use eslint-config-standard-jsx instead of this one. That's why this wasn't included in the major releases of standard@17, because standard itself uses eslint-config-standard-jsx and it's a bit unclear to me whether this module is actually deprecated by that one or not.

[voxpelli]

Note to self:

From the looks of it this is a straight extension on top of the jsx one: c357387

BREAKING: Stop extending from eslint-config-standard-jsx

To update, you will need to:

npm install eslint-config-standard-jsx

And then ensure that "standard-jsx" appears in the "extends" section of your .eslintrc:

"extends": [
"standard-react", "standard-jsx"
]

[flippidippi]

Note to self:

From the looks of it this is a straight extension on top of the jsx one: c357387

BREAKING: Stop extending from eslint-config-standard-jsx
To update, you will need to:
npm install eslint-config-standard-jsx
And then ensure that "standard-jsx" appears in the "extends" section of your .eslintrc:
"extends": [
"standard-react", "standard-jsx"
]

I agree. I feel like these rules should be rolled into eslint-config-standard-jsx

[voxpelli]

@flippidippi The rules in eslint-config-standard-react are the React specific ones on top of the basic JSX ones, so they can't be added to eslint-config-standard-jsx.

Whether it's meaningful to maintain in addition to eslint-config-standard-jsx and possibly creating confusion in how to use them: That can be discussed

[JounQin]

When will this be released??

[mirismaili]

When will this be released???

[flippidippi]

Can we just release this for now until we figure out the jsx vs react direction? I think it makes sense to consolidate those, but until that's done, I feel like this should just be released as is so people can upgrade to 8.

[framerate]

@flippidippi I fear most of us have just moved on to other solutions, this project almost appears abandoned. But hopefully somebody proves me wrong! Big fan

[mkasprz]

Without the release I feel forced to pull version directly from Github as otherwise I expeced some conflict with some other package (I'm not sure which one now, but possibly "@babel/eslint-parser"). Would be grateful for it.

[s100]

It's been six months, this obviously isn't coming. I suggest just stopping using this package.

[voxpelli]

Released as 12.0.0, though I don't use this one myself so please report any bugs back

[mkasprz]

Great, thank You!