Skip to content

v3.0.0
Compare
Choose a tag to compare
@wessberg wessberg released this 30 May 23:32
· 61 commits to master since this release
v3.0.0
2fce040

New Features

rollup-plugin-ts is now based on ESM and requires Node v14.19.0 (BREAKING CHANGE)

Now that TypeScript v4.7 is out, it has finally received great support for ES modules in a Node.js environment that aligns with how it has been implemented across Node.js and browsers.

Because of this, now is a good time to make this plugin a type: "module" package. However, it still provides a CommonJS fallback. If your codebase is still based on CommonJS, you should be fine. Please know however, that rollup-plugin-ts requires an environment running Node v14.19.0 or newer going forward.

TypeScript v4.7 support

rollup-plugin-ts now fully supports TypeScript v4.7 and its new features.
This also means that you can now use .mjs, .mts, .cjs, and .mts files.
Additionally, the extension of your declaration files will depend on the extensions of your output files as controlled by your Rollup config:

  • .js output files will produce .d.ts and optionally .d.ts.map files
  • .mjs output files will produce .d.mts and optionally .d.mts.map files
  • .cjs output files will produce .d.cts and optionally .d.cts.map files

Transpilers are now used for the entire syntax transformation (BREAKING CHANGE)

Before, when you selected a transpiler such as babel or swc, these wouldn't actually be used for stripping away TypeScript-specific features such as types, enums, and decorators. Instead, the TypeScript compiler APIs would still be used for performing the initial syntax transformation, and then babel or swc would "take over from there". However, there are times when you may want to use babel or swc even for the initial transformation.

Going forward, a transpiler will be used for the entire syntax transformation. However, this can be easily customized by mixing transpilers, which is an easy way to get the old behavior back.

Transpilers can be mixed

Now, the transpiler plugin option also accepts an options object if you want to mix them:

ts({
    transpiler: {
        typescriptSyntax: "typescript",
        otherSyntax: "babel"
    }
})

This allows you to decide exactly which transpilers are responsible for which parts of the emit phase. If you want to, in principle you can decide to let swc strip away TypeScript syntax, and then let babel continue on from there. You're in full control.

Of course, it still supports simply accepting a string, like always.

v2.0.7...v3.0.0

Assets 2
Loading