This repo is a continuation of feathers-react-iso-boilerplate, if all you need is an isomorphic feathers react boilerplate you can use git to checkout commit 38bc50ea16f2eab92b5c2bc021ee30771becc920 if the other boilerplate is not available.

After cloning repo you first need to mkdir static-assets/js/ and build the JS files with npm run minvendor and npm run minjs before you run npm start for the first time. Git won't track empty directories, and I try not to track generated files because it would greatly increase the size of my repo.

Dead simple rendering with a custom router and a few components. The conventional wisdom seems to be use a templating engine on top of React, but renderToStaticMarkup is basically the same, so I use it to render my document template. (at least as of this writing, not sure when that was introduced)

Routes config ./src/routes.js Routes paths ./src/components/pages An example of usage is already in each of those destinations.

• Dead simple custom router on the client connects the client React code to the already server rendered React elements.
• Added ./src/components/utils/Link.js Abstracts links and prevents their default behavior so that when JS loads, the router can take over. These are to be used for all internal links. Should be compatible with react-router as of this writing.
• renamed all <a /> tags to <Link /> components.

Isomoriphic usage is domonstrated on the index page: add data, remove data with actions; use of computed to search within the data we already fetched, etc

Persistant data-store in ./src/stores/data.js. with Mongodb Demonstrates

• @observable
• @computed
• @action

Store is consumed in ./src/components/DataList.js, with provider in ./src/components/pages/index.js. Demonstrates

• Provider
• inject
• observer

All files involved with rendering are going to be accessed on the server and client, so to make sure the service doesn't try anything funny on the server we initialize the function (setupDataStore) that integrates the service into the MobX store from the client router.

setupDataStore :

• connect event listeners for [ created , patched , removed ] to the store (client only)
• set initial state by populating from the service