| /** | |
| * Stores are just seed + reduce function. | |
| * Notice they are plain objects and don't own the state. | |
| */ | |
| const countUpStore = { | |
| seed: { | |
| counter: 0 | |
| }, | |
| reduce(state, action) { |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
2015-01-29 Unofficial Relay FAQ
Compilation of questions and answers about Relay from React.js Conf.
Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.
Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).
| #!/bin/bash | |
| # MySQL root password | |
| ROOTPASS='password' | |
| TIMEZONE='Europe/Moscow' | |
| MYSQLPASS=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c12` | |
| SFTPPASS=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c12` | |
| PASSWORD=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c12` | |
| ############## |
| /* | |
| * React.js Starter Kit | |
| * Copyright (c) 2014 Konstantin Tarkus (@koistya), KriaSoft LLC. | |
| */ | |
| 'use strict'; | |
| var Dispatcher = require('../core/Dispatcher'); | |
| var ActionTypes = require('../constants/ActionTypes'); | |
| var SourceTypes = require('../constants/SourceTypes') |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
The basic structure of a React+Flux application (see other examples)
- /src/actions/AppActions.js - Action creators (Flux)
- /src/components/Application.js - The top-level React component
- /src/constants/ActionTypes.js - Action types (Flux)
- /src/core/Dispatcher.js - Dispatcher (Flux)
- /src/stores/AppStore.js - The main store (Flux)
| var format = require('util').format; | |
| var WebpackDevServer = require('webpack-dev-server'); | |
| var webpack = require('webpack'); | |
| var config = require('./webpack.config'); | |
| var argv = require('yargs') | |
| .boolean('h').alias('h', 'hot') | |
| .argv; | |
| var contentBase = { |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
| #!/bin/bash | |
| ############## | |
| echo " | |
| ////////////////////////////////////// | |
| // // | |
| // Welcome to MODx autoinstaller. // | |
| // // | |
| ////////////////////////////////////// |