Package Exports

byots

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (byots) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Bring your own TypeScript

Use the latest TypeScript, with complete access to the compiler API 🌹

Still Just TypeScript

byots will use whatever TypeScript version you install in your application. So you are actually using whatever TypeScript you bring in (recommend npm install typescript@next).

But with the following advantages

Provide ts globally. If you are doing heavy TypeScript work this helps e.g. alm / atom-typescript / tslint all do this.
With a better definition file. We expose the internal APIs (the ones that have /* internal */). It helps experiment by copy pasting from the TypeScript source code.

The definitions are updated daily automatically and our version numbers match the TypeScript nightly version numbers.

Install

In your package.json

npm install byots@latest --save --save-exact

Each release is named after the day it was built and the git commit hash in Microsoft/TypeScript/master that it was built from. We recommend adding save-exact so you know exactly what you tested with.

Usage

Require

Use import * as ts from 'byots' and you get what require('typescript') would give you.

Global `ts`

In addition to returning what typescript returns we also expose ts as a global.

import 'byots';
console.log(ts.createScanner);

Which makes it easy to use the compiler API if you are using it heavily. Note you only need to import once from any file.

About

Note that this is a personal endeavor, not officially by Microsoft.

byots