Release 12.0.0

[voxpelli]

As ESLint 5.0.0 is now released it would be neat to get eslint-config-standard 12.0.0 released as well.

Some stuff should probably be done first though:

Required:

• Change peerDependency to require the stable version
• (anything else?)

Nice to have:

• Merge Update eslint-plugin-node to the latest version 🚀 #108 – moves to newer eslint-plugin-node
• Merge Update eslint-plugin-node to the latest version 🚀 #126 – moves to even newer eslint-plugin-node
• Merge Update eslint-plugin-promise to the latest version 🚀 #128 – moves to latest eslint-plugin-promise
• Maybe merge Add the object-curly-spacing rule #124 (see Release 12.0.0 #123 (comment))
• (anything else?)

[StarpTech]

Does the PR consider also this issue when using eslint 5?

(node:12988) [ESLINT_LEGACY_OBJECT_REST_SPREAD] DeprecationWarning: The 'parserOptions.ecmaFeatures.experimentalObjectRestSpread' option is deprecated. Use 'parserOptions.ecmaVersion' instead. (found in "standard")

[LinusU]

Would be great to get in #124 as well

[yuchonghua]

[voxpelli]

@StarpTech @yuchonghua That should already be fixed in the alpha release of this module, see #117 and 6a89a51, please try that one

[voxpelli]

@LinusU Added that to the list, is a review by @feross or such needed for that to be merged?

[yuchonghua]

When will it be released?
@voxpelli @LinusU

[js-yezi]

[voxpelli]

I guess that #126 should be merged as well before 12.0.0 is released, so that the module is as up to date as possible

[AllenZho]

It seems that all the upgrades with eslint5 are stuck here. Can it be solved as soon as possible? It doesn't have to be solved in the 12.0.0 release, you can solve it at 11.0.0+ first.
/ping @voxpelli @Greenkeeper[bot]

[voxpelli]

@AllenZho See #123 (comment) – ESLint 5 is as far as I understand already supported by the released 12.0.0-alpha.0 and everyone who needs to be able to use ESLint 5 right here and now, and wants to do so without any warnings, can use that version.

Regarding when a stable 12.0.0 can be released – I don't know – I'm not a maintainer – I just opened this issue to help move it along. The only blocker from releasing a stable 12.0.0 is an action from a maintainer – all things outlined in this issue are just extra nice to haves that would be good, but not essential, to get included

[voxpelli]

@LinusU Any feedback on what/who we are waiting on to get this moving? Is it @feross that needs to find time for this or are there some topics that needs further feedback and/or work? And if so: Is there something one can do to help there

[LinusU]

From my side, I'm mostly waiting on @feross.

I would be very happy to move forward with this, but I'm not sure if we have the release process documented somewhere, and I'm not sure if I'm added on npm 🤔

Would be great if you would want to give me some quick directions @feross ☺️ could be anything from "I'll have time soon, please wait" to "added you on npm, please go ahead" ❤️

[macklinu]

I just published eslint-plugin-promise@v4, which supports ESLint v5 (drops support for Node v4). Not sure if that's on your list, but eslint-plugin-promise should no longer block this, if so. 👍

[voxpelli]

@macklinu Great! I added it to the list 👍

[feross]

Thank you to everyone who commented on this issue! ❤️ Especially to @voxpelli and @LinusU for pushing things along.

I'm working to release standard 12 by tonight. Stay tuned!

(And I plan to documenting the release process and get a few others up to speed so I'm not a bottleneck in the future.)

[feross]

eslint-config-standard@12.0.0 is released!