[ { "path": ".babelrc", "content": "{\n \"presets\": [\"react\", \"es2015\", \"stage-0\"],\n\n \"plugins\": [\n \"transform-runtime\",\n \"add-module-exports\",\n \"transform-decorators-legacy\",\n \"transform-react-display-name\"\n ],\n\n \"env\": {\n \"development\": {\n \"plugins\": [\n \"typecheck\",\n [\"react-transform\", {\n \"transforms\": [{\n \"transform\": \"react-transform-catch-errors\",\n \"imports\": [\"react\", \"redbox-react\"]\n }\n ]\n }]\n ]\n }\n }\n}\n" }, { "path": ".editorconfig", "content": "[*]\nindent_style = space\nend_of_line = lf\nindent_size = 2\ncharset = utf-8\ntrim_trailing_whitespace = true\n\n[*.md]\nmax_line_length = 0\ntrim_trailing_whitespace = false\n" }, { "path": ".eslintignore", "content": "webpack/*\nkarma.conf.js\ntests.webpack.js\n" }, { "path": ".eslintrc", "content": "{ \"extends\": \"eslint-config-airbnb\",\n \"env\": {\n \"browser\": true,\n \"node\": true,\n \"mocha\": true\n },\n \"rules\": {\n \"new-cap\": [2, { \"capIsNewExceptions\": [\"List\", \"Map\", \"Set\"] }],\n \"react/no-multi-comp\": 0,\n \"import/default\": 0,\n \"import/no-duplicates\": 0,\n \"import/named\": 0,\n \"import/namespace\": 0,\n \"import/no-unresolved\": 0,\n \"import/no-named-as-default\": 2,\n \"comma-dangle\": 0, // not sure why airbnb turned this on. gross!\n \"indent\": [2, 2, {\"SwitchCase\": 1}],\n \"no-console\": 0,\n \"no-alert\": 0\n },\n \"plugins\": [\n \"react\", \"import\"\n ],\n \"settings\": {\n \"import/parser\": \"babel-eslint\",\n \"import/resolve\": {\n \"moduleDirectory\": [\"node_modules\", \"src\"]\n }\n },\n \"globals\": {\n \"__DEVELOPMENT__\": true,\n \"__CLIENT__\": true,\n \"__SERVER__\": true,\n \"__DISABLE_SSR__\": true,\n \"__DEVTOOLS__\": true,\n \"socket\": true,\n \"webpackIsomorphicTools\": true\n }\n}\n" }, { "path": ".gitignore", "content": ".idea/\nnode_modules/\ndist/\n*.iml\nwebpack-assets.json\nwebpack-stats.json\nnpm-debug.log\n*.swp\n" }, { "path": ".travis.yml", "content": "language: node_js\n\nnode_js:\n - \"0.12\"\n - \"4.0\"\n - \"4\"\n - \"5\"\n - \"stable\"\n\nsudo: false\n\nbefore_script:\n - export DISPLAY=:99.0\n - sh -e /etc/init.d/xvfb start\n\nscript:\n - npm run lint\n - npm test\n - npm run test-node\n" }, { "path": "CONTRIBUTING.md", "content": "# Contributing Guidelines\n\nSome basic conventions for contributing to this project.\n\n### General\n\nPlease make sure that there aren't existing pull requests attempting to address the issue mentioned. Likewise, please check for issues related to update, as someone else may be working on the issue in a branch or fork.\n\n* Non-trivial changes should be discussed in an issue first\n* Develop in a topic branch, not master\n* Squash your commits\n\n### Linting\n\nPlease check your code using `npm run lint` before submitting your pull requests, as the CI build will fail if `eslint` fails.\n\n### Commit Message Format\n\nEach commit message should include a **type**, a **scope** and a **subject**:\n\n```\n (): \n```\n\nLines should not exceed 100 characters. This allows the message to be easier to read on github as well as in various git tools and produces a nice, neat commit log ie:\n\n```\n #459 refactor(utils): create url mapper utility function\n #463 chore(webpack): update to isomorphic tools v2\n #494 fix(babel): correct dependencies and polyfills\n #510 feat(app): add react-bootstrap responsive navbar\n``` \n\n#### Type\n\nMust be one of the following:\n\n* **feat**: A new feature\n* **fix**: A bug fix\n* **docs**: Documentation only changes\n* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing\n semi-colons, etc)\n* **refactor**: A code change that neither fixes a bug or adds a feature\n* **test**: Adding missing tests\n* **chore**: Changes to the build process or auxiliary tools and libraries such as documentation\n generation\n\n#### Scope\n\nThe scope could be anything specifying place of the commit change. For example `webpack`,\n`helpers`, `api` etc...\n\n#### Subject\n\nThe subject contains succinct description of the change:\n\n* use the imperative, present tense: \"change\" not \"changed\" nor \"changes\"\n* don't capitalize first letter\n* no dot (.) at the end\n" }, { "path": "LICENSE", "content": "The MIT License (MIT)\n\nCopyright (c) 2015 Erik Rasmussen\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n" }, { "path": "README.md", "content": "# ⚠️ DO NOT USE THIS!! ⚠️\n\nOnce upon a time, this repo helped a lot of people, but it's _waaaay_ out of date. It's now more of a historical artifact of what React development looked like in 2015.\n\n# React Redux Universal Hot Example\n\n[![build status](https://img.shields.io/travis/erikras/react-redux-universal-hot-example/master.svg?style=flat-square)](https://travis-ci.org/erikras/react-redux-universal-hot-example)\n[![Dependency Status](https://david-dm.org/erikras/react-redux-universal-hot-example.svg?style=flat-square)](https://david-dm.org/erikras/react-redux-universal-hot-example)\n[![devDependency Status](https://david-dm.org/erikras/react-redux-universal-hot-example/dev-status.svg?style=flat-square)](https://david-dm.org/erikras/react-redux-universal-hot-example#info=devDependencies)\n[![react-redux-universal channel on discord](https://img.shields.io/badge/discord-react--redux--universal%40reactiflux-brightgreen.svg?style=flat-square)](https://discord.gg/0ZcbPKXt5bZZb1Ko)\n[![Demo on Heroku](https://img.shields.io/badge/demo-heroku-brightgreen.svg?style=flat-square)](https://react-redux.herokuapp.com)\n[![PayPal donate button](https://img.shields.io/badge/donate-paypal-brightgreen.svg?style=flat-square)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=E2LK57ZQ9YRMN)\n\n---\n\n## About\n\nThis is a starter boilerplate app I've put together using the following technologies:\n\n* ~~Isomorphic~~ [Universal](https://medium.com/@mjackson/universal-javascript-4761051b7ae9) rendering\n* Both client and server make calls to load data from separate API server\n* [React](https://github.com/facebook/react)\n* [React Router](https://github.com/rackt/react-router)\n* [Express](http://expressjs.com)\n* [Babel](http://babeljs.io) for ES6 and ES7 magic\n* [Webpack](http://webpack.github.io) for bundling\n* [Webpack Dev Middleware](http://webpack.github.io/docs/webpack-dev-middleware.html)\n* [Webpack Hot Middleware](https://github.com/glenjamin/webpack-hot-middleware)\n* [Redux](https://github.com/rackt/redux)'s futuristic [Flux](https://facebook.github.io/react/blog/2014/05/06/flux.html) implementation\n* [Redux Dev Tools](https://github.com/gaearon/redux-devtools) for next generation DX (developer experience). Watch [Dan Abramov's talk](https://www.youtube.com/watch?v=xsSnOQynTHs).\n* [React Router Redux](https://github.com/reactjs/react-router-redux) Redux/React Router bindings.\n* [ESLint](http://eslint.org) to maintain a consistent code style\n* [redux-form](https://github.com/erikras/redux-form) to manage form state in Redux\n* [lru-memoize](https://github.com/erikras/lru-memoize) to speed up form validation\n* [multireducer](https://github.com/erikras/multireducer) to combine single reducers into one key-based reducer\n* [style-loader](https://github.com/webpack/style-loader), [sass-loader](https://github.com/jtangelder/sass-loader) and [less-loader](https://github.com/webpack/less-loader) to allow import of stylesheets in plain css, sass and less,\n* [bootstrap-sass-loader](https://github.com/shakacode/bootstrap-sass-loader) and [font-awesome-webpack](https://github.com/gowravshekar/font-awesome-webpack) to customize Bootstrap and FontAwesome\n* [react-helmet](https://github.com/nfl/react-helmet) to manage title and meta tag information on both server and client\n* [webpack-isomorphic-tools](https://github.com/halt-hammerzeit/webpack-isomorphic-tools) to allow require() work for statics both on client and server\n* [mocha](https://mochajs.org/) to allow writing unit tests for the project.\n\nI cobbled this together from a wide variety of similar \"starter\" repositories. As I post this in June 2015, all of these libraries are right at the bleeding edge of web development. They may fall out of fashion as quickly as they have come into it, but I personally believe that this stack is the future of web development and will survive for several years. I'm building my new projects like this, and I recommend that you do, too.\n\n## Installation\n\n```bash\nnpm install\n```\n\n## Running Dev Server\n\n```bash\nnpm run dev\n```\n\nThe first time it may take a little while to generate the first `webpack-assets.json` and complain with a few dozen `[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)` printouts, but be patient. Give it 30 seconds.\n\n### Using Redux DevTools\n\n[Redux Devtools](https://github.com/gaearon/redux-devtools) are enabled by default in development.\n\n- CTRL+H Toggle DevTools Dock\n- CTRL+Q Move DevTools Dock Position\n- see [redux-devtools-dock-monitor](https://github.com/gaearon/redux-devtools-dock-monitor) for more detailed information.\n\nIf you have the \n[Redux DevTools chrome extension](https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd) installed it will automatically be used on the client-side instead.\n\nIf you want to disable the dev tools during development, set `__DEVTOOLS__` to `false` in `/webpack/dev.config.js`. \nDevTools are not enabled during production.\n\n## Building and Running Production Server\n\n```bash\nnpm run build\nnpm run start\n```\n\n## Demo\n\nA demonstration of this app can be seen [running on heroku](https://react-redux.herokuapp.com), which is a deployment of the [heroku branch](https://github.com/erikras/react-redux-universal-hot-example/tree/heroku).\n\n## Documentation\n\n* [Exploring the Demo App](docs/ExploringTheDemoApp/ExploringTheDemoApp.md) is a guide that can be used before you install the kit.\n* [Installing the Kit](docs/InstallingTheKit/InstallingTheKit.md) guides you through installation and running the development server locally.\n* [Adding Text to the Home Page](docs/AddingToHomePage/AddingToHomePage.md) guides you through adding \"Hello, World!\" to the home page.\n* [Adding A Page](docs/AddingAPage/AddingAPage.md) guides you through adding a new page.\n* [React Tutorial - Converting Reflux to Redux](http://engineering.wework.com/process/2015/10/01/react-reflux-to-redux/), by Matt Star\n If you are the kind of person that learns best by following along a tutorial, I can recommend Matt Star's overview and examples.\n\n\n## Explanation\n\nWhat initially gets run is `bin/server.js`, which does little more than enable ES6 and ES7 awesomeness in the\nserver-side node code. It then initiates `server.js`. In `server.js` we proxy any requests to `/api/*` to the\n[API server](#api-server), running at `localhost:3030`. All the data fetching calls from the client go to `/api/*`.\nAside from serving the favicon and static content from `/static`, the only thing `server.js` does is initiate delegate\nrendering to `react-router`. At the bottom of `server.js`, we listen to port `3000` and initiate the API server.\n\n#### Routing and HTML return\n\nThe primary section of `server.js` generates an HTML page with the contents returned by `react-router`. First we instantiate an `ApiClient`, a facade that both server and client code use to talk to the API server. On the server side, `ApiClient` is given the request object so that it can pass along the session cookie to the API server to maintain session state. We pass this API client facade to the `redux` middleware so that the action creators have access to it.\n\nThen we perform [server-side data fetching](#server-side-data-fetching), wait for the data to be loaded, and render the page with the now-fully-loaded `redux` state.\n\nThe last interesting bit of the main routing section of `server.js` is that we swap in the hashed script and css from the `webpack-assets.json` that the Webpack Dev Server – or the Webpack build process on production – has spit out on its last run. You won't have to deal with `webpack-assets.json` manually because [webpack-isomorphic-tools](https://github.com/halt-hammerzeit/webpack-isomorphic-tools) take care of that.\n\nWe also spit out the `redux` state into a global `window.__data` variable in the webpage to be loaded by the client-side `redux` code.\n\n#### Server-side Data Fetching\n\nThe [redux-async-connect](https://www.npmjs.com/package/redux-async-connect) package exposes an API to return promises that need to be fulfilled before a route is rendered. It exposes a `` container, which wraps our render tree on both [server](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/server.js) and [client](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/client.js). More documentation is available on the [redux-async-connect](https://www.npmjs.com/package/redux-async-connect) page.\n\n#### Client Side\n\nThe client side entry point is reasonably named `client.js`. All it does is load the routes, initiate `react-router`, rehydrate the redux state from the `window.__data` passed in from the server, and render the page over top of the server-rendered DOM. This makes React enable all its event listeners without having to re-render the DOM.\n\n#### Redux Middleware\n\nThe middleware, [`clientMiddleware.js`](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/redux/middleware/clientMiddleware.js), serves two functions:\n\n1. To allow the action creators access to the client API facade. Remember this is the same on both the client and the server, and cannot simply be `import`ed because it holds the cookie needed to maintain session on server-to-server requests.\n2. To allow some actions to pass a \"promise generator\", a function that takes the API client and returns a promise. Such actions require three action types, the `REQUEST` action that initiates the data loading, and a `SUCCESS` and `FAILURE` action that will be fired depending on the result of the promise. There are other ways to accomplish this, some discussed [here](https://github.com/rackt/redux/issues/99), which you may prefer, but to the author of this example, the middleware way feels cleanest.\n\n#### Redux Modules... *What the Duck*?\n\nThe `src/redux/modules` folder contains \"modules\" to help\nisolate concerns within a Redux application (aka [Ducks](https://github.com/erikras/ducks-modular-redux), a Redux Style Proposal that I came up with). I encourage you to read the\n[Ducks Docs](https://github.com/erikras/ducks-modular-redux) and provide feedback.\n\n#### API Server\n\nThis is where the meat of your server-side application goes. It doesn't have to be implemented in Node or Express at all. This is where you connect to your database and provide authentication and session management. In this example, it's just spitting out some json with the current time stamp.\n\n#### Getting data and actions into components\n\nTo understand how the data and action bindings get into the components – there's only one, `InfoBar`, in this example – I'm going to refer to you to the [Redux](https://github.com/gaearon/redux) library. The only innovation I've made is to package the component and its wrapper in the same js file. This is to encapsulate the fact that the component is bound to the `redux` actions and state. The component using `InfoBar` needn't know or care if `InfoBar` uses the `redux` data or not.\n\n#### Images\n\nNow it's possible to render the image both on client and server. Please refer to issue [#39](https://github.com/erikras/react-redux-universal-hot-example/issues/39) for more detail discussion, the usage would be like below (super easy):\n\n```javascript\nlet logoImage = require('./logo.png');\n```\n\n#### Styles\n\nThis project uses [local styles](https://medium.com/seek-ui-engineering/the-end-of-global-css-90d2a4a06284) using [css-loader](https://github.com/webpack/css-loader). The way it works is that you import your stylesheet at the top of the `render()` function in your React Component, and then you use the classnames returned from that import. Like so:\n\n```javascript\nrender() {\nconst styles = require('./App.scss');\n...\n```\n\nThen you set the `className` of your element to match one of the CSS classes in your SCSS file, and you're good to go!\n\n```jsx\n
...
\n```\n\n#### Alternative to Local Styles\n\nIf you'd like to use plain inline styles this is possible with a few modifications to your webpack configuration.\n\n**1. Configure Isomorphic Tools to Accept CSS**\n\nIn `webpack-isomorphic-tools.js` add **css** to the list of style module extensions\n\n```javascript\n style_modules: {\n extensions: ['less','scss','css'],\n```\n\n**2. Add a CSS loader to webpack dev config**\n\nIn `dev.config.js` modify **module loaders** to include a test and loader for css\n\n```javascript\n module: {\n loaders: [\n { test: /\\.css$/, loader: 'style-loader!css-loader'},\n```\n\n**3. Add a CSS loader to the webpack prod config**\n\nYou must use the **ExtractTextPlugin** in this loader. In `prod.config.js` modify **module loaders** to include a test and loader for css\n\n```javascript\n module: {\n loaders: [\n { test: /\\.css$/, loader: ExtractTextPlugin.extract('style-loader', 'css-loader')},\n```\n\n**Now you may simply omit assigning the `required` stylesheet to a variable and keep it at the top of your `render()` function.**\n\n```javascript\nrender() {\nrequire('./App.css');\nrequire('aModule/dist/style.css');\n...\n```\n\n**NOTE** In order to use this method with **scss or less** files one more modification must be made. In both `dev.config.js` and `prod.config.js` in the loaders for less and scss files remove \n\n1. `modules`\n2. `localIdentName...`\n\nBefore:\n```javascript\n{ test: /\\.less$/, loader: 'style!css?modules&importLoaders=2&sourceMap&localIdentName=[local]___[hash:base64:5]!autoprefixer?browsers=last 2 version!less?outputStyle=expanded&sourceMap' },\n```\nAfter:\n```javascript\n{ test: /\\.less$/, loader: 'style!css?importLoaders=2&sourceMap!autoprefixer?browsers=last 2 version!less?outputStyle=expanded&sourceMap' },\n```\n\nAfter this modification to both loaders you will be able to use scss and less files in the same way as css files.\n\n#### Unit Tests\n\nThe project uses [Mocha](https://mochajs.org/) to run your unit tests, it uses [Karma](http://karma-runner.github.io/0.13/index.html) as the test runner, it enables the feature that you are able to render your tests to the browser (e.g: Firefox, Chrome etc.), which means you are able to use the [Test Utilities](http://facebook.github.io/react/docs/test-utils.html) from Facebook api like `renderIntoDocument()`.\n\nTo run the tests in the project, just simply run `npm test` if you have `Chrome` installed, it will be automatically launched as a test service for you.\n\nTo keep watching your test suites that you are working on, just set `singleRun: false` in the `karma.conf.js` file. Please be sure set it to `true` if you are running `npm test` on a continuous integration server (travis-ci, etc).\n\n## Deployment on Heroku\n\nTo get this project to work on Heroku, you need to:\n\n1. Remove the `\"PORT\": 8080` line from the `betterScripts` / `start-prod` section of `package.json`.\n2. `heroku config:set NODE_ENV=production`\n3. `heroku config:set NODE_PATH=./src`\n4. `heroku config:set NPM_CONFIG_PRODUCTION=false`\n * This is to enable webpack to run the build on deploy.\n\nThe first deploy might take a while, but after that your `node_modules` dir should be cached.\n\n## FAQ\n\nThis project moves fast and has an active community, so if you have a question that is not answered below please visit our [Discord channel](https://discord.gg/0ZcbPKXt5bZZb1Ko) or file an issue.\n\n\n## Roadmap \n\nAlthough this isn't a library, we recently started versioning to make it easier to track breaking changes and emerging best practices. \n\n* [Inline Styles](docs/InlineStyles.md) - CSS is dead\n\n## Contributing\n\nI am more than happy to accept external contributions to the project in the form of feedback, bug reports and even better - pull requests :) \n\nIf you would like to submit a pull request, please make an effort to follow the guide in [CONTRIBUTING.md](CONTRIBUTING.md). \n \n---\nThanks for checking this out.\n\n– Erik Rasmussen, [@erikras](https://twitter.com/erikras)\n" }, { "path": "api/__tests__/api-test.js", "content": "import {expect} from 'chai';\nimport {mapUrl} from '../utils/url';\n\ndescribe('mapUrl', () => {\n it('extracts nothing if both params are undefined', () => {\n expect(mapUrl(undefined, undefined)).to.deep.equal({\n action: null,\n params: []\n });\n });\n\n it('extracts nothing if the url is empty', () => {\n const url = '';\n const splittedUrlPath = url.split('?')[0].split('/').slice(1);\n const availableActions = {a: 1, widget: {c: 1, load: () => 'baz'}};\n\n expect(mapUrl(availableActions, splittedUrlPath)).to.deep.equal({\n action: null,\n params: []\n });\n });\n\n it('extracts nothing if nothing was found', () => {\n const url = '/widget/load/?foo=bar';\n const splittedUrlPath = url.split('?')[0].split('/').slice(1);\n const availableActions = {a: 1, info: {c: 1, load: () => 'baz'}};\n\n expect(mapUrl(availableActions, splittedUrlPath)).to.deep.equal({\n action: null,\n params: []\n });\n });\n\n it('extracts the available actions and the params from an relative url string with GET params', () => {\n const url = '/widget/load/param1/xzy?foo=bar';\n const splittedUrlPath = url.split('?')[0].split('/').slice(1);\n const availableActions = {a: 1, widget: {c: 1, load: () => 'baz'}};\n\n expect(mapUrl(availableActions, splittedUrlPath)).to.deep.equal({\n action: availableActions.widget.load,\n params: ['param1', 'xzy']\n });\n });\n\n it('extracts the available actions from an url string without GET params', () => {\n const url = '/widget/load/?foo=bar';\n const splittedUrlPath = url.split('?')[0].split('/').slice(1);\n const availableActions = {a: 1, widget: {c: 1, load: () => 'baz'}};\n\n expect(mapUrl(availableActions, splittedUrlPath)).to.deep.equal({\n action: availableActions.widget.load,\n params: ['']\n });\n });\n\n it('does not find the available action if deeper nesting is required', () => {\n const url = '/widget';\n const splittedUrlPath = url.split('?')[0].split('/').slice(1);\n const availableActions = {a: 1, widget: {c: 1, load: () => 'baz'}};\n\n expect(mapUrl(availableActions, splittedUrlPath)).to.deep.equal({\n action: null,\n params: []\n });\n });\n});\n" }, { "path": "api/actions/__tests__/loadInfo-test.js", "content": "import {expect} from 'chai';\nimport loadInfo from '../loadInfo';\nimport timekeeper from 'timekeeper';\n\ndescribe('loadInfo', () => {\n it('loads the current date', () => {\n const now = Date.now();\n timekeeper.freeze(now);\n\n return loadInfo().then(data => {\n expect(data).to.deep.equal({time: now, message: 'This came from the api server'});\n });\n });\n});\n" }, { "path": "api/actions/__tests__/widget-load-test.js", "content": "import {expect} from 'chai';\nimport load from '../widget/load';\nimport sinon from 'sinon';\n\ndescribe('widget load', () => {\n afterEach(()=> {\n if ('restore' in Math.random) {\n Math.random.restore(); // reset the Math.random fixture\n }\n });\n\n describe('successful', () => {\n beforeEach(()=> {\n sinon.stub(Math, 'random').returns(0.4);\n });\n\n it('uses the widgets from the session', () => {\n return load({session: {widgets: ['a', 'b', 'c']}}).then(widgets => {\n expect(widgets.length).to.equal(3);\n });\n });\n\n it('initializes the widgets ', () => {\n return load({session: {}}).then(widgets => {\n expect(widgets.length).to.equal(4);\n expect(widgets[0].color).to.equal('Red');\n });\n });\n });\n\n describe('unsuccessful', () => {\n beforeEach(()=> {\n sinon.stub(Math, 'random').returns(0.2);\n });\n\n it('rejects the call', () => {\n return load({session: {}}).\n then(\n ()=> {\n },\n (err)=> {\n expect(err).to.equal('Widget load fails 33% of the time. You were unlucky.');\n });\n });\n });\n});\n" }, { "path": "api/actions/__tests__/widget-update-test.js", "content": "import {expect} from 'chai';\nimport update from '../widget/update';\nimport * as load from '../widget/load';\nimport sinon from 'sinon';\n\ndescribe('widget update', () => {\n afterEach(()=> {\n if ('restore' in Math.random) {\n Math.random.restore(); // reset the Math.random fixture\n }\n });\n\n describe('randomly successful', () => {\n const widgets = [{}, {id: 2, color: 'Red'}];\n\n beforeEach(()=> {\n sinon.stub(Math, 'random').returns(0.3);\n });\n\n afterEach(()=> {\n if ('restore' in load.default) {\n load.default.restore();\n }\n });\n\n it('does not accept green widgets', () => {\n sinon.stub(load, 'default').returns(new Promise((resolve) => {\n resolve(widgets);\n }));\n return update({session: {}, body: {color: 'Green'}}).\n then(\n ()=> {\n },\n (err)=> {\n expect(err.color).to.equal('We do not accept green widgets');\n });\n });\n\n it('fails to load widgets', () => {\n sinon.stub(load, 'default').returns(new Promise((resolve, reject) => {\n reject('Widget fail to load.');\n }));\n return update({session: {}, body: {color: 'Blue'}}).\n then(\n ()=> {\n },\n (err)=> {\n expect(err).to.equal('Widget fail to load.');\n });\n });\n\n it('updates a widget', () => {\n sinon.stub(load, 'default').returns(new Promise((resolve) => {\n resolve(widgets);\n }));\n const widget = {id: 2, color: 'Blue'};\n return update({session: {}, body: widget}).\n then(\n (res)=> {\n expect(res).to.deep.equal(widget);\n expect(widgets[1]).to.deep.equal(widget);\n });\n });\n });\n\n describe('randomly unsuccessful', () => {\n beforeEach(()=> {\n sinon.stub(Math, 'random').returns(0.1);\n });\n\n it('rejects the call in 20% of the time', () => {\n return update().\n then(\n ()=> {\n },\n (err)=> {\n expect(err).to.equal('Oh no! Widget save fails 20% of the time. Try again.');\n });\n });\n });\n});\n" }, { "path": "api/actions/index.js", "content": "export loadInfo from './loadInfo';\nexport loadAuth from './loadAuth';\nexport login from './login';\nexport logout from './logout';\nexport * as widget from './widget/index';\nexport * as survey from './survey/index';\n" }, { "path": "api/actions/loadAuth.js", "content": "export default function loadAuth(req) {\n return Promise.resolve(req.session.user || null);\n}\n" }, { "path": "api/actions/loadInfo.js", "content": "export default function loadInfo() {\n return new Promise((resolve) => {\n resolve({\n message: 'This came from the api server',\n time: Date.now()\n });\n });\n}\n" }, { "path": "api/actions/login.js", "content": "export default function login(req) {\n const user = {\n name: req.body.name\n };\n req.session.user = user;\n return Promise.resolve(user);\n}\n" }, { "path": "api/actions/logout.js", "content": "export default function logout(req) {\n return new Promise((resolve) => {\n req.session.destroy(() => {\n req.session = null;\n return resolve(null);\n });\n });\n}\n" }, { "path": "api/actions/survey/index.js", "content": "export isValid from './isValid';\n" }, { "path": "api/actions/survey/isValid.js", "content": "export default function survey(req) {\n return new Promise((resolve, reject) => {\n setTimeout(() => {\n const errors = {};\n let valid = true;\n if (~['bobby@gmail.com', 'timmy@microsoft.com'].indexOf(req.body.email)) {\n errors.email = 'Email address already used';\n valid = false;\n }\n if (valid) {\n resolve();\n } else {\n reject(errors);\n }\n }, 1000);\n });\n}\n" }, { "path": "api/actions/widget/index.js", "content": "export update from './update';\nexport load from './load';\n" }, { "path": "api/actions/widget/load.js", "content": "const initialWidgets = [\n {id: 1, color: 'Red', sprocketCount: 7, owner: 'John'},\n {id: 2, color: 'Taupe', sprocketCount: 1, owner: 'George'},\n {id: 3, color: 'Green', sprocketCount: 8, owner: 'Ringo'},\n {id: 4, color: 'Blue', sprocketCount: 2, owner: 'Paul'}\n];\n\nexport function getWidgets(req) {\n let widgets = req.session.widgets;\n if (!widgets) {\n widgets = initialWidgets;\n req.session.widgets = widgets;\n }\n return widgets;\n}\n\nexport default function load(req) {\n return new Promise((resolve, reject) => {\n // make async call to database\n setTimeout(() => {\n if (Math.random() < 0.33) {\n reject('Widget load fails 33% of the time. You were unlucky.');\n } else {\n resolve(getWidgets(req));\n }\n }, 1000); // simulate async load\n });\n}\n" }, { "path": "api/actions/widget/update.js", "content": "import load from './load';\n\nexport default function update(req) {\n return new Promise((resolve, reject) => {\n // write to database\n setTimeout(() => {\n if (Math.random() < 0.2) {\n reject('Oh no! Widget save fails 20% of the time. Try again.');\n } else {\n load(req).then(data => {\n const widgets = data;\n const widget = req.body;\n if (widget.color === 'Green') {\n reject({\n color: 'We do not accept green widgets' // example server-side validation error\n });\n }\n if (widget.id) {\n widgets[widget.id - 1] = widget; // id is 1-based. please don't code like this in production! :-)\n req.session.widgets = widgets;\n }\n resolve(widget);\n }, err => {\n reject(err);\n });\n }\n }, 1500); // simulate async db write\n });\n}\n" }, { "path": "api/api.js", "content": "import express from 'express';\nimport session from 'express-session';\nimport bodyParser from 'body-parser';\nimport config from '../src/config';\nimport * as actions from './actions/index';\nimport {mapUrl} from 'utils/url.js';\nimport PrettyError from 'pretty-error';\nimport http from 'http';\nimport SocketIo from 'socket.io';\n\nconst pretty = new PrettyError();\nconst app = express();\n\nconst server = new http.Server(app);\n\nconst io = new SocketIo(server);\nio.path('/ws');\n\napp.use(session({\n secret: 'react and redux rule!!!!',\n resave: false,\n saveUninitialized: false,\n cookie: { maxAge: 60000 }\n}));\napp.use(bodyParser.json());\n\n\napp.use((req, res) => {\n const splittedUrlPath = req.url.split('?')[0].split('/').slice(1);\n\n const {action, params} = mapUrl(actions, splittedUrlPath);\n\n if (action) {\n action(req, params)\n .then((result) => {\n if (result instanceof Function) {\n result(res);\n } else {\n res.json(result);\n }\n }, (reason) => {\n if (reason && reason.redirect) {\n res.redirect(reason.redirect);\n } else {\n console.error('API ERROR:', pretty.render(reason));\n res.status(reason.status || 500).json(reason);\n }\n });\n } else {\n res.status(404).end('NOT FOUND');\n }\n});\n\n\nconst bufferSize = 100;\nconst messageBuffer = new Array(bufferSize);\nlet messageIndex = 0;\n\nif (config.apiPort) {\n const runnable = app.listen(config.apiPort, (err) => {\n if (err) {\n console.error(err);\n }\n console.info('----\\n==> 🌎 API is running on port %s', config.apiPort);\n console.info('==> 💻 Send requests to http://%s:%s', config.apiHost, config.apiPort);\n });\n\n io.on('connection', (socket) => {\n socket.emit('news', {msg: `'Hello World!' from server`});\n\n socket.on('history', () => {\n for (let index = 0; index < bufferSize; index++) {\n const msgNo = (messageIndex + index) % bufferSize;\n const msg = messageBuffer[msgNo];\n if (msg) {\n socket.emit('msg', msg);\n }\n }\n });\n\n socket.on('msg', (data) => {\n data.id = messageIndex;\n messageBuffer[messageIndex % bufferSize] = data;\n messageIndex++;\n io.emit('msg', data);\n });\n });\n io.listen(runnable);\n} else {\n console.error('==> ERROR: No PORT environment variable has been specified');\n}\n" }, { "path": "api/utils/url.js", "content": "export function mapUrl(availableActions = {}, url = []) {\n const notFound = {action: null, params: []};\n\n // test for empty input\n if (url.length === 0 || Object.keys(availableActions).length === 0) {\n return notFound;\n }\n /*eslint-disable */\n const reducer = (prev, current) => {\n if (prev.action && prev.action[current]) {\n return {action: prev.action[current], params: []}; // go deeper\n } else {\n if (typeof prev.action === 'function') {\n return {action: prev.action, params: prev.params.concat(current)}; // params are found\n } else {\n return notFound;\n }\n }\n };\n /*eslint-enable */\n\n const actionAndParams = url.reduce(reducer, {action: availableActions, params: []});\n\n return (typeof actionAndParams.action === 'function') ? actionAndParams : notFound;\n}\n" }, { "path": "app.json", "content": "{\n \"name\": \"react-redux-universal-hot-example\",\n \"description\": \"Example of an isomorphic (universal) webapp using react redux and hot reloading\",\n \"repository\": \"https://github.com/erikras/react-redux-universal-hot-example\",\n \"logo\": \"http://node-js-sample.herokuapp.com/node.svg\",\n \"keywords\": [\n \"react\",\n \"isomorphic\",\n \"universal\",\n \"webpack\",\n \"express\",\n \"hot reloading\",\n \"react-hot-reloader\",\n \"redux\",\n \"starter\",\n \"boilerplate\",\n \"babel\"\n ]\n}\n" }, { "path": "bin/api.js", "content": "#!/usr/bin/env node\nif (process.env.NODE_ENV !== 'production') {\n if (!require('piping')({\n hook: true,\n ignore: /(\\/\\.|~$|\\.json$)/i\n })) {\n return;\n }\n}\nrequire('../server.babel'); // babel registration (runtime transpilation for node)\nrequire('../api/api');\n" }, { "path": "bin/server.js", "content": "#!/usr/bin/env node\nrequire('../server.babel'); // babel registration (runtime transpilation for node)\nvar path = require('path');\nvar rootDir = path.resolve(__dirname, '..');\n/**\n * Define isomorphic constants.\n */\nglobal.__CLIENT__ = false;\nglobal.__SERVER__ = true;\nglobal.__DISABLE_SSR__ = false; // <----- DISABLES SERVER SIDE RENDERING FOR ERROR DEBUGGING\nglobal.__DEVELOPMENT__ = process.env.NODE_ENV !== 'production';\n\nif (__DEVELOPMENT__) {\n if (!require('piping')({\n hook: true,\n ignore: /(\\/\\.|~$|\\.json|\\.scss$)/i\n })) {\n return;\n }\n}\n\n// https://github.com/halt-hammerzeit/webpack-isomorphic-tools\nvar WebpackIsomorphicTools = require('webpack-isomorphic-tools');\nglobal.webpackIsomorphicTools = new WebpackIsomorphicTools(require('../webpack/webpack-isomorphic-tools'))\n .development(__DEVELOPMENT__)\n .server(rootDir, function() {\n require('../src/server');\n });\n" }, { "path": "circle.yml", "content": "machine:\n node:\n version: 4.0\n environment:\n CONTINUOUS_INTEGRATION: true\n\ndependencies:\n cache_directories:\n - node_modules\n override:\n - npm prune && npm install\n\ntest:\n override:\n - npm run lint\n - npm test\n - npm run test-node\n" }, { "path": "docs/AddingAPage/AddingAPage.md", "content": "# Adding A Hello Page\n\nThis guide adds a `/hello` page to the sample application by \nfollowing the existing outline.\n\n## Using Ack on About\n\nSearching strings is one way to [grok](https://en.wikipedia.org/wiki/Grok) the structure\nof the kit and sample application. You can use *grep* or [ack](http://beyondgrep.com) (`brew install ack`).\nI use *ack* with this alias:\n\n![ick Alias](ick_alias.png)\n\nLooking with `ick about` and ignoring documentation, the word *about* appears in these files:\n\n![ick for About](ick_about.png)\n\n## Add the Hello page container\n\nA new page requires new page renderer. Copy the About page to a \nnew directory and trim out almost all of it:\n\n* `cd ./src/containers && mkdir ./Hello` because each container goes in its own \n directory by convention.\n* `cp About/About.js Hello/Hello.js`\n\nEdit `Hello/Hello.js` into this file:\n\n![New Hello.js](new_hello.png)\n\n\n\n## Edit three files to add Hello\n\n#### Add to `./src/containers/index.js` to include and export the React component:\n\n![Edit index.js](edit_index.png)\n\n#### Add to `./routes.js` to connect the `/hello` url path to the component:\n\n![Edit routes.js 1](edit_route1.png)\n![Edit routes.js 2](edit_route2.png)\n\n#### Add to `./src/containers/App/App.js` to add \"Hello\" to the NavBar\n\n![Edit App.js](edit_app.png)\n\nAnd voila, the new 'Hello' page:\n\n![Show Hello](show_hello.png)\n\n# Take-away: Notice the trade-offs\n\nThe task of adding a new page exemplifies two trade-offs in the kit:\n**code versus convention** and the **cut and paste** style.\n\nConvention is a set of constraining rules that automatically trigger\nroutine configuration tasks. For example, WebPack automatically picked up the \nnew directory `./src/containers/Hello` without adding to any configuration files.\n\nOn the other hand, routine code was added to `./src/containers/index.js` and \n`./src/routes.js` to handle the new page. A convention could automatically\naccomplish the same tasks at either compile or run time. The cost is new \nconstraints, such as requiring `Hello/Hello.js` to be renamed\n`HelloPage/HelloPage.js`.\n\nFollowing a style in the code that has no automatic effects is just organic\ngrowth, not convention. For example, developers reading `./src/containers/index.js`\nmust stop and figure out why all subdirectories except `DevTools` are exported.\n(`DevTools`)[`./src/containers/DevTools/DevTools.js`](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/containers/DevTools/DevTools.js)\ncontains a single function which should be\n[randomly](https://github.com/erikras/react-redux-universal-hot-example/issues/808)\nmoved to `./src/utils` or `./src/helpers`. Using a convention rule that all \ncontainers must contain an exported React component would raise an error.\nOrganic growth leads to disorder in a project.\n\nSimilarly, the **cut and paste** style of coding also degrades the project.\nFor example, In `App.js`, the new *NavItem* tag included a new value for the\n*eventkey* property. The *eventkey* property is\n[poorly](https://github.com/react-bootstrap/react-bootstrap/issues/320)\n[understood](https://github.com/react-bootstrap/react-bootstrap/issues/432).\nAll *eventkey* fields in `App.js` are unused and can be removed. The \n**cut and paste** style just compounds an\n[old error](https://github.com/erikras/react-redux-universal-hot-example/commit/d67a79c1e7da5367dc8922019ca726e69d56bf0e)\nand reinforces confusion.\n\n![Edit App revisted](edit_app2.png)\n\nThe use of the **cut and paste** style raises well known issues in\nmaintenance, documentation, and code quality. It is not for use in\nproduction code. \n\nSome choices about trade-offs are easier than others.\n" }, { "path": "docs/AddingToHomePage/AddingToHomePage.md", "content": "# Adding Hello, World as static text\n\nPrinting *Hello, World!* is a traditional task. This guides you through adding the text \"Hello, World!\" to the\nhome page of the sample application.\n\n## Find the home page\n\nFirst, find the correct file to change by walking through the kit's directory tree:\n\n![Finding The Home Page 1](find_home1.png)\n\n\n![Finding The Home Page 2](find_home2.png)\n\n![Finding The Home Page 3](find_home3.png)\n\n![Finding The Home Page 4](find_home4.png)\n\nSo, the likely file is `src/containers/Home/Home.js`.\n\n## Start the server and open the browser\n\nExecute `npm run dev` and open http://localhost:3000:\n\n* `./package.json`, using [concurrently](https://www.npmjs.com/package/concurrently)\nand [better-npm-run](https://www.npmjs.com/package/better-npm-run), runs \n `./webpack/webpack-dev-server.js` on port 3001; runs `./bin/server.js` for HTTP on port 3000; \n and runs `./bin/api.js` for the REST API on port 3030.\n \n* `./bin/server.js` calls `./src/server.js` and uses the [HMR plugin](http://andrewhfarmer.com/webpack-hmr-tutorial/)\nfor hot reloading, meaning the browser refreshes automatically when any file in `./src` is changed.\n\n* `./webpack/webpack-dev-server` does teh actual compilation with the \n[webpack dev middleware package](https://github.com/webpack/webpack-dev-middleware) to provide a key feature found\nin Glup: compilation without writing intermediate files to disk. Configuring webpack\n[can be confusing](https://medium.com/@dtothefp/why-can-t-anyone-write-a-simple-webpack-tutorial-d0b075db35ed#.cle1vv5ql).\n\n* `./bin/api.js` calls `./api/api.js`. It receives incoming REST requests as JSON objects and responds with\nother JSON objects. \n\n## Change the text\n\nAdd the static text to (`src/containers/Home/Home.js`):\n\n![Add Hello Header to Home](add_home.png)\n\n\nWhen you save the file to disk, the change to the `./src` directory is picked up by the \n[piping](https://www.npmjs.com/package/piping) module, triggering the webpack-dev-server to rebuild \n`./static/dist/[checksum].js`, and triggering a stub injected into the HTML file served to the browser to \nreload. The rebuilding processes through webpack middleware and plugins that compile `*.sccs` files, \ntranspile JAX and ES6 (or ES7), and bundles together all the resources into one package in about 6 seconds.\nThat is, the browser will show \"Hello, World!\" on your web page in about 6 seconds:\n\n![Hello World rendered on home page](hello_rendered.png)\n\n## Conclusion\n\nYou added **Hello, World!**. The process is [as clear as is the summer's sun](https://www.youtube.com/watch?v=EhGiSfv5FJk&t=3m23s).\n\n" }, { "path": "docs/ApiConfig.md", "content": "# Switching to a real API\n\nChances are, once you get comfortable with this setup, you'll want to hook into some existing API rather than use the simple one that comes with this project. Here's how:\n\n## Update `package.json`\n\nFirst things first, you need to add `APIHOST` settings in `package.json`. If you look in `src/config.js`, you'll see that it's already configured to read this `APIHOST` setting if it's present.\n\nIf the port you use differs between your dev & prod API hosts, you may want to get rid of the `APIPORT` setting, including it right in `APIHOST`. Same with the protocol – if you use HTTP in dev but HTTPS in prod, you may want to include the protocol right in `APIHOST`, and then get rid of the explicit `\"http://\"` found in the next section.\n\n## Update `ApiClient`\n\nOpen up `src/helpers/ApiClient.js`. You'll see this line:\n\n``` javascript\n if (__SERVER__) {\n // Prepend host and port of the API server to the path.\n return 'http://' + config.apiHost + adjustedPath;\n }\n```\n\nIf you added `http://` or `https://` to your APIHOST setting, then you need to remove it here.\n\nIn this file, you'll also see that there's a `/api` that gets prepended to the URL when on the client side. That gets routed through a proxy that's configured in server.js, which we'll get to next.\n\nWhy do you need a proxy? So that the `APIHOST` can be set as part of the Node environment, and your client side code can still work. A user's browser doesn't have access to your server's Node environment, so instead the client-side code makes all API calls to this `/api` proxy, which the server configures to hit your real API. That way you can control everything sanely, through environment variables, and set different API endpoints for your different environments.\n\n## Update `server.js`\n\nTo update the proxy, find this chunk in `src/server.js`:\n\n``` javascript\n const proxy = httpProxy.createProxyServer({\n target: 'http://' + config.apiHost,\n ws: true\n });\n```\n\nYou'll want to change this in a few ways:\n\n### 1. Update `target` protocol\n\nIf you changed APIHOST to include the `http://` or `https://` protocol, then get rid of the `'http://' +` in the `target` setting. Note that you'll need to restart your server after making these changes or things will break.\n\n### 2. Decide if you need WebSockets\n\nThe `ws: true` setting is there to support WebSockets connections, which this demo app supports using [socket.io](http://socket.io/). If your API doesn't use WebSockets, then you can remove this line.\n\n### 3. Add a `changeOrigin` setting\n\nThis might be the most important part! It's possible that your API lives at a totally different URL than your front-end app. If that's the case, then you need to add a `changeOrigin` setting. \n\nHere's an example of what the final chunk of code might look like:\n\n``` javascript\n const proxy = httpProxy.createProxyServer({\n target: config.apiHost,\n changeOrigin: true\n });\n```\n\nFinally, after doing all of that, you can get rid of the demo API.\n\n## Get rid of stuff\n\nYou can remove the whole `api` folder, as well as `bin/api.js`.\n\nOnce you do that, you'll also need to remove the lines in `package.json` that called those things. Remove all this:\n\n* ` \\\"npm run start-prod-api\\\"` from the `start` script command\n* ` \\\"npm run start-dev-api\\\"` from the `dev` script command\n* the `start-prod-api` and `start-dev-api` scripts altogether\n* the ` api` argument from the `lint` script\n* the `test-node` and `test-node-watch` scripts, which were there to test the demo API\n* the `start-prod-api` and `start-dev-api` settings in the `betterScripts` section\n\nIf you want, you can also remove all references to `socket`, if you're not using it.\n" }, { "path": "docs/Ducks.md", "content": "This document has found [another, hopefully permanent, home](https://github.com/erikras/ducks-modular-redux).\n\nQuack.\n" }, { "path": "docs/ExploringTheDemoApp/ExploringTheDemoApp.md", "content": "# Guide - Exploring the Demo App\n\nThis guide covers your first look and can be used even before installing software. \n\n## Overview\n\nThis project is a kit for developing interactive applications in JavaScript centered\naround React and Redux. Like all JavaScript kits, it includes a large number of configured\nmodules and a sample, or Demo App, from which to start your application. This guide walks \nthrough that Demo App to show some features and code.\n\n### Open the demo in your browser\n\nThe project hosts a running demo on Heroku, a hosting company. Open \n[https://react-redux.herokuapp.com/](https://react-redux.herokuapp.com/) in your browser to see this page:\n\n![Screenshot](frontpage.png)\n\nMuch of the text is cut-and-paste from the project's \n[README.md](https://github.com/erikras/react-redux-universal-hot-example/blob/master/README.md) file into \nthe code for this page [./src/containers/Home/Home.js](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/containers/Home/Home.js). \n\nThe text provides a one line overview of about twenty of the main \nmodules of hundreds shown during installation. The selection \nand configuration of all these modules is the value of using a kit. When you run across\na module you have never heard of and want to get a quick overview, the fastest way is\nto google for 'slideshare theModuleName' and skim someone's presentation.\n\nThe page is rendered from HTML including React components coded as custom HTML tags.\nThe components use properties to alter appearance and sets of data. Notice some of the components on the page:\n\n![Screenshot with Annotations](frontpage_markup.png)\n\n### Explore the Widgets Page\n\nClick on *Widgets* link on the top of the screen. You come to a page with some arbitrary widgets and more logic\nin the form. Notice how much state affects the display and formatting of buttons:\n\n![Screenshot with Annotations](widgets_markup.png)\n\n### Explore the Survey Page\n\nClick on the *Survey* link. Following the programming style of this kit, the code for this page is \nspread over a [Survey container][scont], a [SurveyForm component][scomp], mentioned in the \n[container][conlist] and [component][complist] lists, \nmentioned in the [routes][routes] function and the navigation of the main [App][app]. The code also uses\nvarious libraries for React, Redux, validation, memoize and other functions. Learn to use [ack](http://beyondgrep.com) \nor the project wide search built into your editor.\n\nTry clicking on the 'Initialize Form' button and then hitting Submit. You will see just an error under\n'Little Bobby Tables'. Now click in the email field then the name field. You now see errors in both\nthe name and the email. Even with a good kit, forms can be difficult to code.\n\n![Screenshot with Annotations](survey_markup.png)\n[scont]: https://github.com/erikras/react-redux-universal-hot-example/tree/master/src/containers/Survey\n[scomp]: https://github.com/erikras/react-redux-universal-hot-example/tree/master/src/components/SurveyForm\n[conlist]: https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/containers/index.js\n[complist]: https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/components/index.js\n[routes]: https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/routes.js\n[app]: https://github.com/erikras/react-redux-universal-hot-example/tree/master/src/containers/App/App.js\n\n### Explore the About Page\n\nClick on the *About* link. The source for this page \n[./src/containers/About/About.js](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/containers/About/About.js)\nuses a casual mix of HTML, ECMA7 JavaScript, and React components. This translates into \nsimple JavaScript code for the browser. Notice how the local state `showKitten` being false causes no\n`div` or `img` tag in the output.\n\n![Screenshot with Annotations](about_markup.png)\n\n### Explore the Login Page\n\nFinally, click on the *Login* page and explore. Looking at the styling for this page \n[./src/containers/Login/Login.scss]](https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/containers/Login/Login.scss)\nwill show an example of how the using styling files litters the code base with extra files. \nConsider the alternative of using \n[Inline Styles](https://github.com/erikras/react-redux-universal-hot-example/blob/master/docs/InlineStyles.md).\n\n# The Take Away\n\nLooking through each page of the DemoApp will lead you to more questions which will keep you \nsearching and learning and you will slowly master this technology.\n\nHere are some additional quests you could undertake:\n\n* How do the About page MiniBar and the status bar share data about the time last loaded?\n* How would you add a fourth counter that incremented by two? How many files would you need\n to touch?\n* What order are calls made when you click \"Reload Widgets\" on the widgets page?\n* Why does surveyValidation use memoize?\n\nInstall, hack, explore!\n\n*All guides are works in progress, and pull requests are always welcome. If you make an\naccepted pull request and live in Silicon Valley, I'll treat you to coffee. -- Charles*\n\n\n" }, { "path": "docs/InlineStyles.md", "content": "# Inline Styles\n\nIn the long term, CSS, LESS and SASS are dead. To keep this project on the bleeding edge, we should drop SASS support in favor of inline styles.\n\n## Why?\n\nI think the case is made pretty strongly in these three presentations.\n\nChristopher Chedeau | Michael Chan | Colin Megill\n--- | --- | ---\n[![CSS In Your JS by Christopher Chedeau](https://i.vimeocdn.com/video/502495328_295x166.jpg)](http://blog.vjeux.com/2014/javascript/react-css-in-js-nationjs.html) | [![Michael Chan - Inline Styles: themes, media queries, contexts, & when it's best to use CSS](https://i.ytimg.com/vi/ERB1TJBn32c/mqdefault.jpg)](https://www.youtube.com/watch?v=ERB1TJBn32c) | [![Colin Megill - Inline Styles are About to Kill CSS](https://i.ytimg.com/vi/NoaxsCi13yQ/mqdefault.jpg)](https://www.youtube.com/watch?v=NoaxsCi13yQ)\n\nClearly this is the direction in which web development is moving.\n\n## Why not?\n\nAt the moment, all the inline CSS libraries suffer from some or all of these problems:\n\n* Client side only\n* No vendor auto prefixing (requires `User-Agent` checking on server side)\n* No server side media queries, resulting in a flicker on load to adjust to client device width\n\nIdeally, a library would allow for all the benefits of inline calculable styles, but, in production, would allow some generation of a CSS block, with media queries to handle device width conditionals, to be inserted into the page with a `