amcdnl

Why I hate TypeScript

Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.

Not Standard

TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.

Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.

Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!

davisml

// AttributedString class from https://github.com/cohitre/attributedString.js
// Modifications made to support html tags & remove span wrapper from unstyled blocks
var AttributedString = (function () {
  var aString
    , StringRange
    , RangesList
    , HtmlSerializer
    , plainStringSerializer
    , _ = {}
    , entityMap = {

daviferreira

'use strict';

var babel = require('babel-core');
var fs = require('fs');

// borrowed from https://github.com/babel/babel-jest/blob/master/index.js
require.extensions['.jsx'] = function (module, filename) {
  var src = fs.readFileSync(filename, 'utf8');
  // Allow the stage to be configured by an environment
  // variable, but use Babel's default stage (2) if

StephanHoyer

'use strict';

var Octokat = require('octokat');
var extend = require('lodash/object/assign');

var defaults = {
  branchName: 'master',
  token: '',
  username: '',
  reponame: ''

timoxley

// this will find all files ending with _test.js and run them with Mocha. Put this in your package.json


"scripts": {
  "test": "find ./tests -name '*_test.js' | xargs mocha -R spec"
},