If you're using only nginx (no Apache thx) and want to serve your projects using a local dev domain.
brew install nginx
Or download/unzip for Win: http://nginx.org/en/docs/windows.html
If you're using only nginx (no Apache thx) and want to serve your projects using a local dev domain.
brew install nginx
Or download/unzip for Win: http://nginx.org/en/docs/windows.html
import React from 'react' | |
const provideContext = (contextKey, contextType) => ( | |
React.createClass({ | |
childContextTypes: { | |
[contextKey]: contextType | |
}, | |
getChildContext() { | |
const { children, ...props } = this.props |
Small script for development + builds with browserify.
Uses loose-envify
for faster inlining and cross-env
to handle windows/unix shells.
Dev features:
Build features:
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
# Hello, and welcome to makefile basics. | |
# | |
# You will learn why `make` is so great, and why, despite its "weird" syntax, | |
# it is actually a highly expressive, efficient, and powerful way to build | |
# programs. | |
# | |
# Once you're done here, go to | |
# http://www.gnu.org/software/make/manual/make.html | |
# to learn SOOOO much more. |
// array utils | |
// ================================================================================================= | |
const combine = (...arrays) => [].concat(...arrays); | |
const compact = arr => arr.filter(Boolean); | |
const contains = (() => Array.prototype.includes | |
? (arr, value) => arr.includes(value) | |
: (arr, value) => arr.some(el => el === value) |
varying vec2 vUv; | |
uniform sampler2D tDiffuse; | |
uniform sampler2D tColorLUT; | |
uniform vec2 resolution; | |
#pragma glslify: blendOverlay = require(./glsl-blend-overlay) | |
#pragma glslify: displace = require(./glsl-displace) | |
#pragma glslify: srcOver = require(./glsl-src-over) | |
#pragma glslify: colorCorrect = require(glsl-lut/flipY) |
While trying to explain Flux to a friend using words, I realized that a diagram's worth a thousand of them, and went with this.
+---------------------+
| |
| Dispatcher |
+-->| +---------------+
| +----------|----------+ |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.