| import * as models from "models"; | |
| import Sequelize from "sequelize"; | |
| import fs from "fs"; | |
| delete models.default; | |
| const sequelize = new Sequelize( | |
| '', | |
| '', | |
| '', { |
This is how I configured the deploy of my rails apps to AWS Elastic Beanstalk through CircleCI 1.0.
If you are using the Circle CI 2.0, take a look at this article from ryansimms
On Project Settings > Environment Variables add this keys:
| import React, { PropTypes } from 'react'; | |
| import { TransitionMotion, spring } from 'react-motion'; | |
| /** | |
| * One example of using react-motion (0.3.0) within react-router (v1.0.0-rc3). | |
| * | |
| * Usage is simple, and really only requires two things–both of which are | |
| * injected into your app via react-router–pathname and children: | |
| * | |
| * <RouteTransition pathname={this.props.pathname}> |
NOTE: I could not get VS2013 to compile node modules (sigh) so this uses VS2010.
Following this issue, http://blogs.msdn.com/b/vcblog/archive/2011/03/31/10148110.aspx.
First you need to install prerequisites
| // Velocity Animate | |
| // ================ | |
| // | |
| // Inspired by https://gist.github.com/tkafka/0d94c6ec94297bb67091. | |
| // | |
| // Extend so it supports: | |
| // | |
| // 1) A transition object in the same format as the ones in the library below, | |
| // directly to the component. Example: | |
| // |
| /** | |
| * Simple userland heapdump generator using v8-profiler | |
| * Usage: require('[path_to]/HeapDump').init('datadir') | |
| * | |
| * @module HeapDump | |
| * @type {exports} | |
| */ | |
| var fs = require('fs'); | |
| var profiler = require('v8-profiler'); |
This is a companion Gist for a talk that I gave at React Berlin in April 2015. The fine folks at Bitcrowd recorded all three of the evening's talks, so you can watch mine at https://www.youtube.com/watch?v=9ArhJiMGVDc.
Peter Magenheimer (@peterjmag)
I'm a front end developer at ResearchGate. And yes, we're hiring.
…specifically React 0.13 using ES6 class syntax
Originally I was implementing the validator as a context, but then I got stung by parent context vs owner context. I'll likely return to the context model when React's context implementation is more final (looks like they're moving towards parent context over owner context, which I'd prefer).
This document will help you generate flamegraphs for your node processes on OS X.
You can read about the various types of flamegraphs and how they are useful
in Brendan Gregg's wonderful write up here.
By the end of this document, you should have a flamegraph for you node app to play with.
| 'use strict'; | |
| require('harmony-reflect'); | |
| /** | |
| * Here we should not use 'harmony-reflect', but | |
| * es6 proxies directly from a harmony | |
| * implementation. Traceur-compiler / | |
| * react-tools es6 transform dont provide | |
| * proxies as the implementation would affect |
