tjFogarty

// inject bower components
gulp.task('wiredep', function () {
    gulp.src('./partials/*.php')
        .pipe(wiredep({
            directory: './bower_components/'
        }))
        .pipe(gulp.dest('./partials'));
});

tjFogarty

/* globals $, jQuery, Foundation */
/* jshint node:true */

'use strict';

window.MQ = (function(MQ, $, queries) {

  /**
   * $cache elements
   * @type {Object}

tjFogarty

<img

srcset="/path/to/slider-image-small.jpg 400w,
/path/to/slider-image-medium.jpg 800w,
/path/to/slider-image-large.jpg 1200w"

sizes="100vw"

alt="...">

fideloper

<?php

/**
 * Intention:
 *
 * "testing" environment has a SQLite database configured
 * Run migrations against --env=testing
 *
 * Separate seeds run here per test method will delete the SQLite
 * code tables, and re-create them with codes that fit the needs

tjFogarty

<picture>
	<!--[if IE 9]><video style="display: none;"><![endif]-->
	<source srcset="{{ slide.image_desktop | tojpg | resize(1200) }}" media="(min-width: 1000px)">

	<source srcset="{{ slide.image_tablet | tojpg | resize(800) }}" media="(min-width: 767px)">

	<source srcset="{{ slide.image | tojpg | resize(480) }}, {{ slide.image | tojpg | resize(766) }} 2x" media="(max-width: 766px)">
	<!--[if IE 9]></video><![endif]-->

	<img class="slider__image" srcset="{{ slide.image_tablet | tojpg | resize(800) }}"	alt="{{ slide.title }}">

treyrich

angular.module("MyApp", ["SocketProvider"])
.controller("MyController", ["$scope", "socket", function($scope, socket) {

    // Fetch initial data
    $scope.person = null;
    socket.get("/person/1").success(function(data) {

        $scope.person = data;

    }).error(function() {

jodyheavener

Inspired by this issue, with these instructions you should be able to get Babel transpiling your JS in Sails JS for the client side.

1. Install Grunt Babel npm install --save grunt-babel
2. Create a babel.js file under tasks/config and add something like the following:

module.exports = function(grunt) {

    grunt.config.set('babel', {
dev: {

Sewdn

TL;DR

Meteor is great at sharing code between different builds for different platforms. You can use the same source for your browser builds, server builds, your builds for iOS, Android, ... But how to organize your project to be able to orchestrate your builds for different apps and services from the same source? This post elaborates on the reasons why you need these different builds and how you could accomplish this with Meteor easily.

Use cases: Why would you build different apps?

1. Different apps for different roles

Say you have an app with completely different end user experiences depending on their role. It is common practice to have the user logged in, check her authorization (role) and then setup different routes or load different templates to serve that type of user’s needs. While doing so, all types of users load the same build and the app decides what portions of the build to use and what not to use.

connor

// NOTE: I added the .js extension to this gist so it would have syntax highlighting. This file should have NO file extension

{
    // Settings
    "passfail"      : false,  // Stop on first error.
    "maxerr"        : 100,    // Maximum error before stopping.


    // Predefined globals whom JSHint will ignore.
    "browser"       : true,   // Standard browser globals e.g. `window`, `document`.

JedWatson

To implement API authentication in KeystoneJS, you need the following:

For key based authentication

• Middleware that validates the key in the request body or a header

For session based authentication

• An endpoint that handles signin
• An endpoint that handles signout