fabiomaggio

1. Clone project

2. Checkout all branches that contain the files that should be moved

3. Delete the remote

4. Run the filter-branch command:

   git filter-branch --tree-filter 'mkdir -p /path/to/tmp; mv * /path/to/tmp; mkdir subdir; mv /path/to/tmp/* subdir/' --tag-name-filter cat --prune-empty -- --all

   • All files are first copied to a temporary dir and move from there to the new destination

• Existing tags are updated

datchley

React/Redux Style Guide

Table of Contents:

• React/Redux Style Guide
  • React Guidelines
    • Organization
    • Components
• Container Components

justinph

let Nightmare = require('nightmare');
let harPlugin = require('nightmare-har-plugin');
let options = {
  waitTimeout: 1000
};

harPlugin.install(Nightmare);

let nightmare = Nightmare(Object.assign(harPlugin.getDevtoolsOptions(), options));

hallettj

# Makefile for transpiling with Babel in a Node app, or in a client- or
# server-side shared library.

.PHONY: all clean

# Install `babel-cli` in a project to get the transpiler.
babel := node_modules/.bin/babel

# Identify modules to be transpiled by recursively searching the `src/`
# directory.

fotinakis

/*
This is an example of how to add special CSS that only applies in Percy's
rendering environment, for example to hide certain dynamic elements.

This is a bit of hack, we don't guarantee this will work forever in Percy
and we'll be adding a more officially-supported mechanism for this.
*/
@-moz-document domain(proxyme.percy.io) {
  #flappy-div {
    visibility: hidden !important;

dchowitz

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

jimfb

class MyWrapper {
  return React.Children.only(this.props.children);
}


class MyLibraryComponent {
  render() {
    return <div><span><whatever><MyWrapper ref=...>{this.props.statelessComponentThatIWantToReference}</MyWrapper></whatever></span></div>;
  }

seblambla

/*
Author: ZetCoby
http://stackoverflow.com/a/30376660/3708754
*/

var tools = {
  /**
   *
   * Used to get the length of a rect
   *

einfallstoll

Installation for GUI Users

1. Right click the file and choose information and choose to always open this file with Terminal.app

2. Go to the Terminal.app and do something like this chmod 744 Reset Spotlight.sh

3. There you go, you can now double click it so reset the Spotlight location

4. Optional: Uncomment line for the useCount to prevent Spotlight to forget that you already used it

Joris-van-der-Wel

'use strict';
var profiler = require('v8-profiler');
profiler.startProfiling();

// ...

var cpuProfile = profiler.stopProfiling();
require('fs').writeFileSync(__dirname + '/foo.cpuprofile', JSON.stringify(cpuProfile));