conorhastings

/* this lacks subscribe behavior or ability to dispatch from outside of component tree but that is generally not neccesary */
class State extends React.Component {
  constructor(props) {
    super(props); 
    this.state = YOUR_INITIAL_STATE;
  }
  reducer = (action, state, props) => {...newState};
  /* setState takes an object of new state as first arg or a function of props and state that returns new state 
   * which we will use here
   * we pass dispatch around and use it similarly to redux dispatch

nottrobin

#! /usr/bin/env python

from base64 import b64decode
from github import Github

with open('access-token.txt') as token_file:
    token = token_file.read().strip()

api = Github(token)
site = api.get_repo('nottrobin/gh-cms-example-site')

vkostyukov

API	Status Codes
[Twitter][tw]	200, 304, 400, 401, 403, 404, 406, 410, 420, 422, 429, 500, 502, 503, 504
[Stripe][stripe]	200, 400, 401, 402, 404, 429, 500, 502, 503, 504
[Github][gh]	200, 400, 422, 301, 302, 304, 307, 401, 403
[Pagerduty][pd]	200, 201, 204, 400, 401, 403, 404, 408, 500
[NewRelic Plugins][nr]	200, 400, 403, 404, 405, 413, 500, 502, 503, 503
[Etsy][etsy]	200, 201, 400, 403, 404, 500, 503
[Dropbox][db]	200, 400, 401, 403, 404, 405, 429, 503, 507

danielkhan

/**
 * Simple userland CPU profiler using v8-profiler
 * Usage: require('[path_to]/CpuProfiler').init('datadir')
 *
 * @module CpuProfiler
 * @type {exports}
 */

var fs = require('fs');
var profiler = require('v8-profiler');

ryanflorence

// make a "base" component
const FakeButton = (props) => (
  <div
    {...props}
    style={{
      cursor: 'default',
      border: '1px solid',
      borderRadius: '3px',
      ...props.style
    }}

paulirish

What forces layout / reflow

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.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

roman01la

var acorn = require('acorn'); // parser
var esrecurse = require('esrecurse'); // walker
var t = require('ast-types').builders; // ast types
var escodegen = require('escodegen'); // generator

/* parse -> walk -> types -> generate */

var ast = acorn.parse('var x = 23 * 576;'); // code -> ast

// traverse ast

ryanflorence

Hi Zach :D

Modals are funny beasts, usually they are a design cop-out, but that's okay, designers have to make trade-offs too, give 'em a break.

First things first, I'm not sure there is such thing as a "simple" modal that is production ready. Certainly there have been times in my career I tossed out other people's "overly complex solutions" because I simply didn't understand the scope of the problem, and I have always loved it when people who have a branch of experience that I don't take the time

domenic

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

• It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
• It is free, with no quotas.
• Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

ericelliott

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).