unional

[alias]
	lo = log --oneline
	# Push upstream
	pu = push -u origin HEAD
	co = checkout
	# Purge branches deleted in remote (e.g. in GitHub)
	pb = !git branch -vv | grep ': gone]' | awk '{print $1}' | xargs git branch -D
[pull]
	rebase = true
[core]

unional

[{
  "name": "npm",
  "patterns": [{
    "pattern": "package.json",
    "syntax": ["json"],
    "order": [      
    ]
  }]
}]

unional

# update local to remove all remote-tracking branches
git fetch --all -p

# remove local branches with no remote branches
git branch -vv | grep ': gone]' | awk '{print $1}' | xargs git branch -D

unional

{
  "release": {
    "analyzeCommits": {
      "releaseRules": [
        {
          "breaking": true,
          "release": "minor"
        }
      ]
    }

unional

#! /bin/bash

# Thanks to Night Train:
# https://stackoverflow.com/questions/48250235/how-to-setup-travis-to-skip-script-on-particular-nodejs-version
# https://docs.travis-ci.com/user/customizing-the-build/#Implementing-Complex-Build-Steps
#
# To use this, create this file (e.g. under scripts folder: ./scripts/run-on-node-version.sh)
# and give it execution permission: chmod ugo+x scripts/run-on-node-version.sh
# Then you can use it in CI configurations, e.g. .travis.yml:
#   - ./scripts/run-on-node-version.sh latest "npm install --no-save coveralls && npm run coveralls"

unional

branches:
  only:
    - master
    - /^greenkeeper.*$/

# vs

branches:
  except:
    - /^v\d+\.\d+\.\d+$/

unional

const EventEmitter = require('events')

const emitter = new Eventemitter()

function shouldNotThrow() {
  try {
    emitter.emit('x')
  }
  catch {
    // unfortunately, error is thrown

unional

How to write typings

When you write typed definitions for DefinitelyTyped, you create a pull request on DefinitelyTyped with the corresponding .d.ts file and you are done. In the .d.ts file you write either an ambient internal module or ambient external module as in the handbook.

Things are a little bit different when you write a typings.

While it is definitely not harder then writing typed definitions for DefinitelyTyped, there isn't a clear term or reference on how to write a typings.

First things first...terminology

Going through the handbook and spec to understand everything you need to write typings is a great thing to do, but it isn't fun. Also, since TypeScript is rapidly improving, some information in the handbook is out of date.

unional

export interface InstallOptions {
  cwd: string;
  /**
   * If not specified, will benerate both "browser.d.ts" and "main.d.ts"
   **/
  env?: "browser" | "main" | string[];
  production: boolean; // Q: Not sure if this should be part of public API
}

export interface Typings {

unional

export interface InitOptions {
  cwd: string;
  upgrade?: boolean;
}

export interface typings {
  init(options: InitOptions): void
}