Eslint-plugin-react: Publish a new release?

[andrew-humu]

Sorry for the nuisance issue, but is there any chance we could get a new release cut soon?

I notice that it's been about three months since the last release now, and there appear to be several new rules, tweaks and fixes that have yet to be published.

Thanks for all the great work!

[peterwiebe]

@yannickcr 🙏🏽

[ljharb]

There's no need to ping people individually, or even to file this issue :-). When someone has time, a release will be cut, and prior to that, a release is impossible - because nobody has the time to do it.

[peterwiebe]

@ljharb my bad :( I will note that for the future. If there is anything I can do to help lighten your load feel free to msg me.

[andrew-humu]

Sorry, I didn't mean to cause anyone any stress.

I'm just excited about some of the latest changes, and looking forward to getting my hands on them!
(Especially this rule, now that babel@7 has landed: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-fragments.md)

I occasionally need a little nudge to remember to keep on top of projects I'm helping to maintain, so I thought maybe a polite request would be forgivable. 🙂

[dimitarnestorov]

Decided to make a simple script that publishes every commit to master on npm https://www.npmjs.com/package/eslint-plugin-react-nightly

Switching to it requires you to:

1. npm install --save-dev eslint-plugin-react-nightly
2. Switch from react to react-nightly in your plugins section of your ESLint config
3. And the hideous part, find and replace every rule from react/ to react-nightly/

Hope that this is helpful to anyone.
Improvements can be requested at the repo https://github.com/dimitarnestorov/eslint-plugin-react-nightly-script

[ljharb]

You’re certainly free to do that, but that’s not actually helping anything - all it’s going to do is make bug reports harder to triage and solve, which will take up even more of our time.

[dimitarnestorov]

5 minutes after posting I realized that if you want to get the latest commit in your dependencies all you have to do is change your package.json to point to the repo like in the screenshot below and running npm install.

Should I unpublish the package?

[ljharb]

Good call, and yeah, I’d suggest that ¯\_(ツ)_/¯ since you can install from github, that seems like a much easier approach that makes it an explicit choice by the user to use an unstable version.

[dimitarnestorov]

Done

[ljharb]

v7.12.0 is released.