JamieMason

/*------------------------------------*\
    $OVERRIDES

$animation-name    : $english-quotes    : $responsive          : $palm-pull
$arrow             : $font-size         : $responsive-extra    : $palm-push
$arrow-border      : $from              : $state               : $portable-pull
$arrow-color       : $giga-size         : $to                  : $portable-push
$arrow-edge        : $global-border-box : $truncation-boundary : $property
$arrow-location    : $half-spacing-unit : $use-arrows          : $pull
$arrow-size        : $i                 : $use-beautons        : $push

JamieMason

/*
.accessibility     .code-comment       .informative              .nav--stacked
.additional        .delta              .island                   .numbered-list
.all-cols          .epsilon            .islet                    .numerical
.alpha             .extra-help         .kilo                     .options
.beta              .flexbox            .label                    .pagination
.block-list        .flexbox__item      .landmark                 .pill
.block-list__link  .flyout             .lead                     .proceed
.brand             .flyout--alt        .lede                     .rule
.brand-color       .flyout__content    .line-numbers             .rule--dashed

JamieMason

function replaceReturnedValue(returnStatement) {
  returnStatement.type = 'ExpressionStatement',
  returnStatement.expression = {
    type: 'CallExpression',
    callee: {
      type: 'MemberExpression',
      computed: false,
      object: {
        type: 'Identifier',
        name: '_map'

JamieMason

Hey, Probably a somewhat n00b question, but on sites of your size that build and release as often as yours do - how do you manage your npm and bower packages? Currently we .gitignore our node_modules and bower_components directories, but I feel we should break that SPOF we have with npm and bower's servers, in the event they're unavailable when our CI is running a build/release.

I had considered checking the packages into git, but;

1. I'm sure this is frequently advised against [citation needed].
2. Some packages such as karma-runner/karma-phantomjs-launcher perform a tailored installation for the OS npm install was run from (eg phantomjs for Windows if installed when on Windows) - so if developer A on Windows runs npm install and checks it into git, CI Server B on Linux will be failing builds.

Is this SPOF something you're even concerned about? And if so, how do you manage it please?

JamieMason

LinkedIn.com imported contacts, filter out connections that do not have a LinkedIn account.

Navigate to https://www.linkedin.com/people/contacts, open your browser Developer console and run;

[].forEach.call(document.querySelectorAll('li.vcard'), function(el) {
  if (!el.querySelector('span.in-icon')) {
    el.parentNode.removeChild(el);
  }
});

JamieMason

{
  "showInfo": true,
  "showRulers": false,
  "showExtensionLines": false,
  "contentColor": {
    "r": 111,
    "g": 168,
    "b": 220,
    "a": 0.66
  },

JamieMason

function getDepth($scope) {
  var depth = 0;
  while ($scope.$parent) {
    $scope = $scope.$parent;
    depth++;
  }
  return depth;
}

console.log(

JamieMason

#!/bin/bash

# Runs our end to end tests in casperjs.
# Run this script as follows from the project root;
#
#     bin/run_e2e_tests

printf "\e[93m > SEARCHING FOR TEST FILES \033[0m \n"

find "$PWD" -iname "*.e2e.spec.js" -type f -print0 | while read -d '' -r file; do

JamieMason

'use strict';

module.exports = {
  create: create
};

var path = require('path');
var terminal = require('terminal');

function create(options) {

JamieMason

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console