Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Create React Apps with No Configuration

facebook.github.io

Post reply on HN
Print view View original

61–70 of 250 posts

Re: Create React Apps with No Configuration

#61

Post by Exuma »

JoeCortopassi wrote: post #33

This is great for someone who wants to get started to learn React, but is missing a ton that is needed for a real world production app. * No isomorphic rendering * No hot module replacement * No generators * No dockerization * No Sass support * No test environment setup * No code splitting It would be cool to have a production ready tool from Facebook, but I'll stick with gluestick for now https://github.com/TrueCar/…

Dockerization, are you crazy? This is just a simple boilerplate. If you want something absurdly complicated (and frustrating to work with imo), use something like Este https://github.com/este/este

Re: Create React Apps with No Configuration

#62

Post by sotojuan »

seangrogg wrote: post #58

I think one of the best things I've done to date is actually distance myself from the React community. While I love some of the tooling that has come out of it (Redux, React-Router) I think the community (as an amorphous entity) over-emphasizes the need/desire for transpiling, linting, testing, etc. Since then, I've "reverted" to building things in ES5, working in multiple files without bundling, etc. and I have to s…

I was just talking about this with coworkers... I love React but the community (aside from the actual creators and leaders like Dan) is too much for me and seem to love bloat and unnecessary features. The cynical side of me thinks a lot just do it for GitHub stars and blog views, but maybe not.

Of course, we just spent two days trying to decipher a React/Redux project whose lead dev decided to use every "latest" feature even though it's a good ol' CRUD app.

Re: Create React Apps with No Configuration

#63

Post by seangrogg »

griffinmichl wrote: post #41
amavisca wrote: post #5

Under the hood this is Webpack + Babel + ESLint with sane initial configuration. Love it.

This is all I ever want in a React boilerplate, but everyone feels the need to throw a bunch of random shit into them that others probably do not even want. Glad they kept it sane and simple.

In all fairness, I think that flags that provide some basic bootstrapping for Redux and/or React-Router would be very spiffy - those tools are useful for many React applications.

Re: Create React Apps with No Configuration

#64

Post by danabramov »

ctvo wrote: post #57
orf wrote: post #25

> Having just attended EmberCamp a week ago, I was excited about Ember CLI. Ember users have a great “getting started” experience thanks to a curated set of tools united under a single command-line interface. This is one of the best things about Ember. `ember new`, `ember serve`, ember generate component my-component`, `ember build`, `ember deploy`, `ember install`. It's opinionated but it lets you get productive rig…

Kind of interesting to think about the two projects and how they diverge based on the core developers. Ember is made by folks who work on / for small and medium companies[1]. They don't have the build infrastructure Facebook does and are able to create an anointed solution in Ember-CLI because they'll use it daily. React is stuck in a place where the environment it's developed in is unique from what any other user wi…

This is a very accurate description of the problem. We’re optimistic though. I’m sure that the community will help make Create React App even better.

Re: Create React Apps with No Configuration

#66

Post by afarrell »

thereact wrote: post #26

This is great since it provides an OFFICIAL opinionated set of tools for building React apps which is typically the largest barrier of entry for new developers looking to experiment with this technology. However, it is missing a lot of core features that typically come standard with Webpack/React boilerplates. Directly from their Github: Some features are currently not supported: Server rendering. Testing. Some exper…

Lack of testing is a pretty big oversight given how helpful testing is for someone getting started. Hopefully it is easy to just add mocha on top of this with out any mucking around?

Re: Create React Apps with No Configuration

#67

Post by seangrogg »

JoeCortopassi wrote: post #40
mumphster wrote: post #36

Earlier quoted context omitted.

None of that is needed for a real world production frontend app, with the exception of maybe tests.

Granted, some things like hot module replacement and generators are not necessary, most of the others are (isomorphic rendering, code splitting, sass, dockerization). I'm not saying you need those things for your personal react app going into production, but when dealing with bigger teams for a critical app they really become important tools

In all fairness, most "critical apps" won't be using a standardized boilerplate anyways. It makes little sense to optimize for the least-likely consumer.

Re: Create React Apps with No Configuration

#68

Post by danabramov »

sotojuan wrote: post #62
seangrogg wrote: post #58

I think one of the best things I've done to date is actually distance myself from the React community. While I love some of the tooling that has come out of it (Redux, React-Router) I think the community (as an amorphous entity) over-emphasizes the need/desire for transpiling, linting, testing, etc. Since then, I've "reverted" to building things in ES5, working in multiple files without bundling, etc. and I have to s…

I was just talking about this with coworkers... I love React but the community (aside from the actual creators and leaders like Dan) is too much for me and seem to love bloat and unnecessary features. The cynical side of me thinks a lot just do it for GitHub stars and blog views, but maybe not. Of course, we just spent two days trying to decipher a React/Redux project whose lead dev decided to use every "latest" feat…

We think ES6 is not the problem here. It’s just a language, and arguably a better one than ES5.

The problem is the low level tooling around it. This is what we’re trying to fix with this project. Hopefully you’ll give it a go, and maybe it will give you just as much enjoyment as using tags. If not, please let us know how we can improve.

It’s not linting/transpilation/bundling that’s bad, it’s that it’s hard to do them without shooting yourself in the foot.

Re: Create React Apps with No Configuration

#69

Post by seangrogg »

sotojuan wrote: post #62
seangrogg wrote: post #58

I think one of the best things I've done to date is actually distance myself from the React community. While I love some of the tooling that has come out of it (Redux, React-Router) I think the community (as an amorphous entity) over-emphasizes the need/desire for transpiling, linting, testing, etc. Since then, I've "reverted" to building things in ES5, working in multiple files without bundling, etc. and I have to s…

I was just talking about this with coworkers... I love React but the community (aside from the actual creators and leaders like Dan) is too much for me and seem to love bloat and unnecessary features. The cynical side of me thinks a lot just do it for GitHub stars and blog views, but maybe not. Of course, we just spent two days trying to decipher a React/Redux project whose lead dev decided to use every "latest" feat…

Yeah, this is basically what kills it for me. When I was unemployed and just building random apps for fun it was great that there was a lot of ongoing progress and evolution in the React community. But when I came back a few months later to show off an app the npm install process let me know everything was deprecated - a bit vexing to consider how much work would be required to keep my shitty side projects up-to-date - not even considering actually building new features into them.

Re: Create React Apps with No Configuration

#70

Post by sotojuan »

danabramov wrote: post #68
sotojuan wrote: post #62

Earlier quoted context omitted.

I was just talking about this with coworkers... I love React but the community (aside from the actual creators and leaders like Dan) is too much for me and seem to love bloat and unnecessary features. The cynical side of me thinks a lot just do it for GitHub stars and blog views, but maybe not. Of course, we just spent two days trying to decipher a React/Redux project whose lead dev decided to use every "latest" feat…

We think ES6 is not the problem here. It’s just a language, and arguably a better one than ES5. The problem is the low level tooling around it. This is what we’re trying to fix with this project. Hopefully you’ll give it a go, and maybe it will give you just as much enjoyment as using tags. If not, please let us know how we can improve. It’s not linting/transpilation/bundling that’s bad, it’s that it’s hard to do the…

I definitely use ES6 for sure, though nothing too crazy (no decorators, bind :: thingy, etc).

Do you remember how you were telling people on Twitter that they don't need every single crazy feature and every single thing in the Redux store (or even Redux at all) to do React? The kind of people I am complaining about are the ones that say the opposite.

Post reply on HN