TypeScript loader for SystemJS

A plugin for SystemJS which enables you to System.import TypeScript files directly. The files are compiled in the browser and compilation errors written to the console.

plugin-typescript uses TypeScript 1.8.x
For TypeScript 1.7.5 and below use plugin-typescript 2.x.x

Starting with JSPM 0.17.0 (currently in beta) this plugin will be the officially supported mechanism for transpiling TypeScript. It provides the ability to type-check files while loading them, which is not currently possible with the built-in SystemJS TypeScript transpiler.

Add SystemJS map configuration for plugin-typescript and typescript:

SystemJS.config({
  map: {
    "ts": "path/to/plugin-typescript/lib/plugin.js",
    "typescript": "path/to/typescript/lib/typescript.js"
  }
});

Install plugin-typescript like this:

jspm install ts

System.config({
  transpiler: "ts"
  packages: {
    "app": {
      "defaultExtension": "ts",
    }
  }
});

This will tell SystemJS to transpile all modules (.js and .ts) using plugin-typescript.

System.config({
  transpiler: "plugin-babel",
  packages: {
    "src": {
      "defaultExtension": "ts",
      "meta": {
        "*.ts": {
          "loader": "ts"
        }
      }
    }
  }
});

This will cause all .ts files in the "src" package to be loaded through plugin-typescript.

See the example projects contained within this repository for a working setup.

Configuration settings can be passed to the compiler via "typescriptOptions":

System.config({
  typescriptOptions: {
    module: "system",
    noImplicitAny: true,
    typeCheck: true,				// also accepts "strict"
    tsconfig: true                  // also accepts a path
  }
});

All the usual TypeScript compiler options are supported, as well as these additional ones:

A boolean flag which controls whether the files are type-checked or simply transpiled. Type-checking does add some overhead to the build process as typings need to be loaded and the compiler has more work to do.

By default compiler errors are written to the console but the build is allowed to continue. To change this behaviour you can use typeCheck: "strict" in which case the build will be failed when compiler errors are encountered.

A boolean flag which instructs the plugin to load configuration from "tsconfig.json". To override the location of the file set this option to the path of the configuration file, which will be resolved using normal SystemJS resolution.

Compiler options which do not conflict with those required by plugin-typescript will be loaded from the compilerOptions section of the file. Any declaration files contained in the files array will also be loaded if type-checking is enabled.

Specify whether to use lib.d.ts targetLib: "es5" or lib.es6.d.ts targetLib: "es6" (default)

(deprecated)

A boolean flag which controls how triple-slash references are resolved. When it is set then SystemJS will be used to resolve reference files, so

/// <reference path="./common/angular.d.ts" />

will resolve relative to the current directory because of the "./", but

/// <reference path="angular2/bundles/typings/angular2/angular2.d.ts" />

will resolve to jspm_packages/npm/[email protected]/bundles/typings/angular2/angular2.d.ts

The default value is false. As it is incompatible with other tools (editors etc), this setting is deprecated in favour of using typings as described below.

When true, the type-checker will automatically resolve any file with a .html extension to have a default export which is a string. This enables importing of html templates using plugin-text with full type-checking and no errors.
(this feature will be removed when microsoft/TypeScript#6615 becomes available)

When compiling in the browser, compiler errors contain a link to the exact location of the error in the source. This is particularly helpful if you are using Chrome DevTools as your IDE.

This plugin provides incremental type-checking when using systemjs-hot-reloader See any of the example projects for a working hot-reloading setup.

The plugin will automatically load typings for packages if it knows that they are present. In order tell the plugin that a package exposes external typings, use SystemJS metadata configuration which can be specified in packages configuration or in the jspm registry.

  packages: {
    "angular2": {
      "meta": {
        "*.js": {
          "typings": true     // can also be path of a typings bundle 
        }
      }
    }
  }

If external typings are present for all js files in the package set "typings": true. If external typings are in a single bundled file then specify the path of that file, relative to the root of the project.
For more information on setting SystemJS metadata, see here

The type-checker runs across multiple packages if the imported file resolves to a typescript file. This means that if you do import "mypackage/index" and that resolves to a typescript file then that import will be properly type-checked. You no longer have to handcraft an external declaration file for 'mypackage'.

To override the version of TypeScript used by the plugin, add an override to the jspm section of your package.json

	"devDependencies": {
		"css": "systemjs/[email protected]",
		"ts": "frankwallis/plugin-typescript@^4.0.5"
	},
	"overrides": {
		"github:frankwallis/[email protected]": {
	 		"dependencies": {
	    		"typescript": "npm:[email protected]"
	  		}
		}
	}

To run the example projects:

> git clone https://github.com/frankwallis/plugin-typescript.git
> cd plugin-typescript
> npm install
> cd examples/react  		// or examples/angular2 or examples/angular
> jspm install
> npm start

To bundle each example project:

> npm run build 			// or jspm bundle-sfx src build/build.js