schmod

schmod

global =
{
  background: 'background_color',
  foreground: '',
  invisibles: '',
  lineHighlight: 'highlight_color',
  selection: ''
}

styles = 

schmod

{
    'targets' : [
        {
            'target_name' : 'winpty-agent',
            'type' : 'executable',
            'include_dirs' : [
                'include',
            ],
            'defines' : [
                'UNICODE',

schmod

schmod

/*global module:false*/
module.exports = function(grunt) {

  // Project configuration.
  grunt.initConfig({
    modernizr: {
        'devFile': 'remote',
        'outputFile': 'modernizr.js',
        'extra': {
        },

schmod

{
  "plugins": ["babel-plugin-transform-es2015-block-scoping", "./plugin"]
}

schmod

import angular from 'angular';
import moment from 'moment';

export default angular.module('foo', [])
.run(function(){
    window.foo = moment();
});

schmod

var myMod = (function () {
'use strict';

var commonjsGlobal = typeof window !== 'undefined' ? window : typeof global !== 'undefined' ? global : typeof self !== 'undefined' ? self : {}

function interopDefault(ex) {
	return ex && typeof ex === 'object' && 'default' in ex ? ex['default'] : ex;
}

function createCommonjsModule(fn, module) {

schmod

/*

  This is a quick-and-dirty script to reprocess files that have been partially-processed by aws-lambda-redshift-loader,
  if an error has left entries in your LambdaRedshiftProcessedFiles DynamoDB table that don't have corresponding entries
  in the LambdaRedshiftBatches table (and therefore cannot be easily reprocessed by any of the tools bundled with 
  aws-lambda-redshift-loader).

  You'll need to enter a few configuration details about your AWS account and S3 bucket, and run query.js to generate
  a list of S3 keys that you'd like to retry.  

schmod

A quick example demonstrating how to use elasticsearch.js, Bluebird, and AWS Elasticsearch with TypeScript.

You'll need to install a few dependencies and types:

npm install --save @types/elasticsearch @types/http-aws-es elasticsearch http-aws-es bluebird

If you're using AWS Elasticsearch, provide an ES_TYPE environment variable set to aws, as well as values for AWS_ACCESS_KEY, AWS_SECRET_KEY, and AWS_REGION. (I make this configurable so it's easy to point applications at a local ES instance when developing/testing locally, and at AWS when deployed to production)