They are specifically working on it according to this React.js Conf talk [0].

There's also rwb from Pete Hunt [1].

EDIT: Removed comment about 'standard'. Ain't so bad anymore apparently.

[0] https://www.youtube.com/watch?v=-RJf2jYzs8A#t=00h14m25s

[1] https://github.com/petehunt/rwb/

> the most obnoxious style-guide of all

What do you mean? I've heard people say that a couple times but they never really elaborated. Do people love their semicolons that much? Are people offended that it's called "standard"? Or something else?

> They are specifically working on it according to this React.js Conf talk

This is very exciting. I prefer React over Vue, but one of the things I love about Vue is vue-cli[0]. Something similar, if not better, for React, would be greatly appreciated.

[0] https://vuejs.org/2015/12/28/vue-cli/

Tbf I just looked over 'standard' and it's improved a ton since it initially came out. Bar one minor rule, the only rule I still object to is the semicolon one, which I'm obvs not going to get into a discussion about, because I value my sanity. I'll edit my above comment if I still can :)

There also exists semistandard, just for you :)

Which this tool doesn't integrate with...? Ultimately, that's always the problem with these "get-started-quickly" tools.

Semis aside, I take issue with the name and the badge[0], making it seem like _the_ style of writing JS instead of just _a_ style. The contents of the project are fine, but this aspect is misleading for people new to JS.

[0]: https://camo.githubusercontent.com/e06d9d72eecca61c1ba39fdf1...

using the name standard is just harmful when your linter doesn't follow a rule (yes semicolons) that 90% of the codebases use.

It's interesting how the Facebook team decided to do a built-in all-in-one opinionated CLI for React Native but never did for regular React. Hope they get around to this soon.

+1

would love more "explicit (in code) best practices" if possible even a "recommended default approach"

i understand that a full "framework" is not the way to for the community. but a few default standards would be good as guidance for newcomers and to manage expectations of coders coming into existing projects

To be fair, this is just packaging up a fairly standard webpack config with a nice CLI: https://github.com/olahol/reactpack/blob/master/config.js

So, it can be extended or changed as the whims of the JS community migrate between tools and practices.

Would it kill them to write "npm install"?

Honestly... I just just think we need to wait for front end develop-{ment,ers} to mature. Let's give them (us?) 5-10 years to settle this.

Meanwhile: Do what you've been doing so far[1] and... stay calm. Stop worrying.

[1] The assumption being that it works for you.

EDIT: Almost everything you hear about in the start of the hype cycle is NOT going to go anywhere. Conclusion: Chill.

I don't think you're reading the situation accurately. Debating and improving our development tools is a sport across the entire field of programming.

The status quo already is to keep on using what we're using. That doesn't need to be said. But if it wasn't for our endless search for nirvana, people would be stuck on Vim and 4-space tabs.

No developer left behind.