Can we mark this as deprecated?

[bearcott]

It is clear no one has been maintaining this for nearly 4 months. 60+ pull requests and 200+ issues...

[jdosullivan]

+1

[sauravskumar]

+1

[nattaponw]

+1

[OKNoah]

Seems like @erikras has been busy with http://redux-form.com/6.0.2/. Cut him some slack.

[bearcott]

@OKNoah I understand that its very hard for a single person to keep up with projects at this scale. However, this is the first result on google when searching "react redux universal app." If this repo will not be further maintained we must mark it deprecated and point to an actively maintained repo otherwise we're just being irresponsible as a community.

[bertho-zero]

Waiting you can watch my fork, all the dependencies are updated and I added a few things, especially for the back-end.

First I updated packages (including redux-form v6), implemented React Hot Reload and removed react-transform-hmr.

As proposed in a pull request for this project I set up Happypack to boost the first build of "npm run dev", more details here (pull).

I updated the travis.yml because times have changed ..

Here is the most interresting part, the API is really light in my opinion so I added Feathers, all that was there before is still, and I even create a basic-api branch for more reticent.
Feathers provides aspect-oriented programing, aspects are recurrent problematics that we can meet by creating a site, authentication is one aspect, the payment is another, etc.

But what Feathers? It's a very lightweight package npm, an overlay of express which allows use of services such as middleware, and their hooks. There are an events system in real-time and their filters Everything else is optional (even hooks). It is simple to call on the client side an it's usable in the same way in http and socket, without events for the http obviously. All known websockets system and/or fetcher (providers) can be used, database adapters, and/or mailers also...

I added authentication, the connection is synchronized between the socket and http connection. You can use any passport strategy, there are now local, token and facebook for oauth example. The socket user's connection is identical to that used in http, the same user with the same verification.
There is a secure chat socket as example.

As before it's simple to dispose of socket if you don't need.
The user and the token are available in the action handler already existing.

I created a hook to validate the data that is based on the client validator, with the access to the service to check the uniqueness of an email for example.

There are also error handling, logging and debugging.

I am working to add the support of offline mode with service-worker through sw-precache.

All this is on the progressive branch, soon master. (Demo running on heroku)

[Nepoxx]

You can take a look at https://github.com/sahat/megaboilerplate which is actively maintained and has a great React "starter kit".