rav94

#!/bin/bash

# current Git branch
branch=$(git symbolic-ref HEAD | sed -e 's,.*/\(.*\),\1,')

# current project name
projectName=$(git config --local remote.origin.url|sed -n 's#.*/\([^.]*\)\.git#\1#p')

# establish master branch name variables
masterBranch=$branch

cowboy

import axios from 'axios'

let mockingEnabled = false

const mocks = {}

export function addMock(url, data) {
  mocks[url] = data
}

Rich-Harris

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

dmvaldman

Promises as EventEmitters

I was trying to understand JavaScript Promises by using various libraries (bluebird, when, Q) and other async approaches.

I read the spec, some blog posts, and looked through some code. I learned how to

salcode

# Current branch - Determine current git branch, store in $currentbranch, and exit if not on a branch
if ! currentbranch=$(git symbolic-ref --short -q HEAD)
then
	echo We are not currently on a branch.
	exit 1
fi

# Uncommited Changes - Exit script if there uncommited changes
if ! git diff-index --quiet HEAD --; then
	echo "There are uncommited changes on this repository."

tracker1

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used

bugventure

module.exports = function chain() {
    var steps = Array.apply(null, arguments);

    return function middleware(req, res, next) {
        (function dequeue() {
            var step = steps.shift(),
                callback = steps.length ? function (err) {
                    if (err) {
                        return next(err);
                    }

elijahmanor

describe("getTweets - Server", function () {
    var server, fakeData = [ /* ... */ ];

    before(function () {
        // Doesn’t work :( It’s JSONP!
        server = sinon.fakeServer.create();
        server.respondWith(
            "GET", 
            "https://api.twitter.com/.../elijahmanor.json?count=5",
            [200, { "Content-Type": "application/json" }, JSON.stringify(fakeData)]

chriscoyier

@media only screen and (min-width: 320px) {

  /* Small screen, non-retina */

}

@media
only screen and (-webkit-min-device-pixel-ratio: 2)      and (min-width: 320px),
only screen and (   min--moz-device-pixel-ratio: 2)      and (min-width: 320px),
only screen and (     -o-min-device-pixel-ratio: 2/1)    and (min-width: 320px),