rollup-plugin-typescript2

Rollup plugin for typescript with compiler errors.

This is a rewrite of original rollup-plugin-typescript, starting and borrowing from this fork.

This version is somewhat slower than original, but it will print out typescript syntactic and semantic diagnostic messages (the main reason for using typescript after all).

Usage

// rollup.config.js
import typescript from 'rollup-plugin-typescript2';

export default {
    entry: './main.ts',

    plugins: [
        typescript()
    ]
}

The plugin depends on existence of tsconfig.json file. All compiler options and file lists are loaded from that.

Following compiler options are forced though:

• module: es2015
• sourceMap: true
• noEmitHelpers: true
• importHelpers: true
• noResolve: false

Plugin takes following options:

• check: true

  Set to false to avoid doing any diagnostic checks on the code.

• verbosity: 2

  Goes up to 3.

• clean: false

  Set to true for clean build (wipes out cache on every build).

• cacheRoot: ".rts2_cache"

  Path to cache.

• include: [ "*.ts+(|x)", "**/*.ts+(|x)" ]

  Passes all .ts files through typescript compiler.

• exclude: [ "*.d.ts", "**/*.d.ts" ]

  But excludes types.

• abortOnError: true

  Bail out on first syntactic error. In most cases setting this to false will result in exception in rollup itself.

• rollupCommonJSResolveHack: false

  On windows typescript resolver favors POSIX path, while commonjs plugin (and maybe others?) uses native path as module id. This can result in namedExports being ignored if rollup happened to use typescript's resolution. Set to true to pass resolved module path through resolve() to match up with commonjs.

TypeScript version

This plugin currently requires TypeScript 2.0+.

Reporting bugs

Report any bugs on github: https://github.com/ezolenko/rollup-plugin-typescript2/issues.

Attach your tsconfig.json, package.json (for versions of dependencies), rollup script and anything else that could influence module resolution, ambient types and typescript compilation.

Check if problem is reproducible after running npm prune to clear any rogue types from npm_modules (by default typescript grabs all ambient types).

Check if you get the same problem with clean option set to true (might indicate a bug in the cache).

If makes sense, check if running tsc directly produces similar results.

Attach plugin output with verbosity option set to 3 (this will list all files being transpiled and their imports).