5 ms·

I wish we had something like this officially backed by the react team. In 30 minutes when a new standard approach comes out, this tool will become obsolete.

by tomtau 10y ago

andreasklinger 10y ago
+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
timdorr 10y ago
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 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.
nilliams 10y ago
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 https://www.youtube.com/watch?v=-RJf2jYzs8A#t=00h14m25s [1] https://github.com/petehunt/rwb/ https://github.com/petehunt/rwb/
- clessg 10y ago
  > 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/ https://vuejs.org/2015/12/28/vue-cli/
  - lowboy 10y ago
    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/e06d9d72eecca61c1ba39fdf19868f70fcb3a9b3/68747470733a2f2f63646e2e7261776769742e636f6d2f6665726f73732f7374616e646172642f6d61737465722f62616467652e737667 https://camo.githubusercontent.com/e06d9d72eecca61c1ba39fdf1...
    - patates 10y ago
      using the name standard is just harmful when your linter doesn't follow a rule (yes semicolons) that 90% of the codebases use.
  - nilliams 10y ago
    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 :)
    - SOLAR_FIELDS 10y ago
      There also exists semistandard, just for you :)
      - Nullabillity 10y ago
        Which this tool doesn't integrate with...? Ultimately, that's always the problem with these "get-started-quickly" tools.
- sotojuan 10y ago
  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.
lomnakkus 10y ago
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.
- danneu 10y ago
  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.
pbreit 10y ago
Would it kill them to write "npm install"?

I wish we had something like this officially backed by the react team. In 30 minutes when a new standard approach comes out, this tool will become obsolete.

by tomtau 10y ago

I wish we had something like this officially backed by the react team. In 30 minutes when a new standard approach comes out, this tool will become obsolete.

andreasklinger 10y ago

+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

timdorr 10y ago

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 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.

nilliams 10y ago

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 https://www.youtube.com/watch?v=-RJf2jYzs8A#t=00h14m25s [1] https://github.com/petehunt/rwb/ https://github.com/petehunt/rwb/

clessg 10y ago
> 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/ https://vuejs.org/2015/12/28/vue-cli/
- lowboy 10y ago
  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/e06d9d72eecca61c1ba39fdf19868f70fcb3a9b3/68747470733a2f2f63646e2e7261776769742e636f6d2f6665726f73732f7374616e646172642f6d61737465722f62616467652e737667 https://camo.githubusercontent.com/e06d9d72eecca61c1ba39fdf1...
  - patates 10y ago
    using the name standard is just harmful when your linter doesn't follow a rule (yes semicolons) that 90% of the codebases use.
- nilliams 10y ago
  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 :)
  - SOLAR_FIELDS 10y ago
    There also exists semistandard, just for you :)
    - Nullabillity 10y ago
      Which this tool doesn't integrate with...? Ultimately, that's always the problem with these "get-started-quickly" tools.
sotojuan 10y ago
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.

lomnakkus 10y ago

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.

danneu 10y ago
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.

pbreit 10y ago

Would it kill them to write "npm install"?