Add transforms for TypeScript

[dantman]

TypeScript's transforms are a bit different from Babel's resulting in globalize-compiler not always working on pre-compiled TypeScript code.

The following basic example will be transpiled by TypeScript as such:

import Globalize from 'globalize';

Globalize.formatDate(new Date());

"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
exports.__esModule = true;
var globalize_1 = __importDefault(require("globalize"));
globalize_1["default"].formatDate(new Date());

Sometimes you cannot configure aliases to override globalize to the globalize-runtime so it's reasonable to require globalize-runtime directly. In TypeScript this would be transpiled as such.

import Globalize from 'globalize/dist/globalize-runtime';

Globalize.formatDate(new Date());

"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
exports.__esModule = true;
var globalize_runtime_1 = __importDefault(require("globalize/dist/globalize-runtime"));
globalize_runtime_1["default"].formatDate(new Date());

[rxaviers]

LGTM. Please how can we test these changes?

[dantman]

globalize-compiler didn't have tests for the Babel behaviour so I wasn't sure how to add tests for the TypeScript behaviour.

To test yourself you could use node bin/globalize-compiler.js -l en -o test-out.js test.js and put the transpiled JS code I've provided into test.js.

If you run that on the stable version, it won't find any formatters and will error out. If you try it on the PR version it will find the transpiled formatter and output like normal.

If you wanted you could also validate the TypeScript output I provided. You should just need to run npx -p typescript tsc --esModuleInterop test.ts with the example TypeScript code in test.ts.