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. However we highly recommend npm install typescript@next byots@latest so you don't get any type definition - JavaScript inconsistencies.

But with the following advantage

With a liberal definition file. We expose internal APIs.

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 import * as ts from 'typescript' would give you.

Alternatives

ts-expose-internals

https://github.com/nonara/ts-expose-internals

ts-expose-internals builds for new releases only to provide better stability - byots is nightly for bleeding edge experimentation.
ts-expose-internals uses module augmentation so you import typescript - byots reexports typescript so you import byots.