zwacky

var gulp = require('gulp');
var plugins = require('gulp-load-plugins')();
var rimraf = require('rimraf');

var paths = {
  less: ['./less/*.less'],
  js: ['./js/app/*.js', './js/app/**/*.js'],
  jsView: ['./js/app/views/*.html'],
  dist: {
    css: './public/css/',

kuy

#!/bin/sh

matches=$(git diff --cached | grep -E '\+.*?FIXME')

if [ "$matches" != "" ]
then
        echo "'FIXME' tag is detected."
        echo "Please fix it before committing."
        echo "  ${matches}"
        exit 1

jobsamuel

Run NodeJS as a Service on Ubuntu 14.04 LTS

With Node you can write very fast JavaScript programs serverside. It's pretty easy to install Node, code your program, and run it. But > how do you make it run nicely in the background like a true server?

• Go to /etc/init/
• $ sudo vim yourapp.conf
• Paste script.conf
• $ sudo start yourapp
• And when you wanna kill the process $ sudo stop yourapp

addyosmani

CSS Layout Debugger

A tweet-sized debugger for visualizing your CSS layouts. Outlines every DOM element on your page a random (valid) CSS hex color.

One-line version to paste in your DevTools

Use $$ if your browser aliases it:

~ 108 byte version

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.

rtrouton

#!/bin/bash

# Installing the Xcode command line tools on 10.7.x or higher

osx_vers=$(sw_vers -productVersion | awk -F "." '{print $2}')
cmd_line_tools_temp_file="/tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress"

# Installing the latest Xcode command line tools on 10.9.x or higher

if [[ "$osx_vers" -ge 9 ]]; then

paulirish

/* bling.js */
window.$ = document.querySelector.bind(document);
window.$$ = document.querySelectorAll.bind(document);
Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
NodeList.prototype.__proto__ = Array.prototype;
NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };

loadedsith

# Description:
#   emoji.coffee - Replaces :text: or text with emojis.
#   Great for IRC or anywhere not already emojified.
#
# Dependencies:
#   None
#
# Configuration:
#   None
#

rikukissa

title	slug	createdAt	language	preview
Unit testing Angular.js app with node.js, mocha, angular-mocks and jsdom	unit-testing-angular-js-app-with-node	2015-07-05T18:04:33Z	en	Majority of search result about unit testing Angular.js apps is about how to do it by using test frameworks that run the tests in a real browser. Even though it's great to be able to test your code in multiple platforms, in my opinion it creates a lot of boilerplate code and makes it hard to run the tests in, for instance a CI-server.

Testing Angular.js app headlessly with node.js + mocha

Lean unit tests with minimal setup

bithoundio

{
  "ignore": [
    "**/deps/**",
    "**/node_modules/**",
    "**/thirdparty/**",
    "**/third_party/**",
    "**/vendor/**",
    "**/**-min-**",
    "**/**-min.**",
    "**/**.min.**",