chore(deps-dev): bump rollup-plugin-ts from 1.4.7 to 2.0.4

[dependabot]

Bumps rollup-plugin-ts from 1.4.7 to 2.0.4.

Release notes

Sourced from rollup-plugin-ts's releases.

v2.0.4

• fix: regression in v2.0.3 on TypeScript <= 3.7 where ExportDeclarations could be dropped f56c91c

wessberg/rollup-plugin-ts@v2.0.3...v2.0.4

v2.0.3

• fix: group ExportDeclarations by not just module specifiers but also whether or not they or their individual ExportSpecifiers are &#39;isTypeOnly&#39;. Fixes #153 493014c

wessberg/rollup-plugin-ts@v2.0.2...v2.0.3

v2.0.2

• feat: add TypeScript v4.5 support dffc8b7

wessberg/rollup-plugin-ts@v2.0.1...v2.0.2

v2.0.1

• fix: fix a problem with resolving swc configs 677c928
• docs: documented how to opt out of @​babel-preset-env c791d88

wessberg/rollup-plugin-ts@v2.0.0...v2.0.1

v2.0.0

Breaking Changes

Babel packages are now optional peer dependencies

Ever since rollup-plugin-ts was initially released, it has declared hard dependencies on several babel packages such as @babel/core, @babel/runtime, @babel/preset-env, and @babel/plugin-transform-runtime. This is useful when configuring the plugin to use Babel as the transpiler. However, it also meant that a ton of Babel-related packages was installed for everyone who wanted to use rollup-plugin-ts, but not necessarily Babel, at least not on every project. It also took away control from library consumers in terms of deciding which specific versions of Babel and its related packages to depend on. And, it also meant that if the plugin should support additional transpilers in the future, the related packages to those would most likely also have to be declared as hard dependencies, to align with the behavior with Babel.

With v2.0.0, all Babel dependencies are now optional peer dependencies. That means that if you use the transpiler: "babel" option with rollup-plugin-ts, you'll have to make sure that @babel/core, @babel/runtime, @babel/plugin-transform-runtime, and @babel/preset-env are declared as dependencies within your package.json file. If you don't, you'll get an error describing exactly which packages are missing such that you can easily include these in your package.json file.

New Features

Support for using swc as a transpiler

It was always the intention that rollup-plugin-ts could be extended to support more transpilers than just typescript and babel. Now that we support optional peer dependencies, it was finally possible to bring swc support to the plugin.

Swc is a much faster alternative to Babel, built in Rust, that attempts to be as close to a drop-in replacement for Babel as possible. It is not nearly as mature and doesn't have as big a plugin ecosystem yet, but can often be much faster than Babel. And like Babel, it also has first-class support for Browserslists which will be used to decide which syntax transformations to apply depending on language support in the target environments.

Full Changelog

• docs: improve README 80b7d1c
• docs: fix incorrect formatting in README ee9ab26
• docs: Document interoperability with swc in README 68474f4
• fix: when emiting declarations, always use define for class fields to work around limitations introduced in TypeScript 4.3 for when bundling declarations when a subclass overrides a property from the parent class but doesn&#39;t provide an initializer b25a494
• fix: add support for shimming regenerator-runtime when using swc as a transpiler 1513fc5
• feat: add support for swc as a transpiler as an alternative to babel. #155 e84d21c
• feat: no longer depend on @​babel/core types in npm package d91ec74
• BREAKING CHANGE: Move babel related dependencies to peer dependencies and make them optional cfe3913
• fix: ensure that the drive letter is prefixed to absolute paths on Windows when getSourceFile is called internally from TypeScript f368af3
• test: make more tests run in serial 12a3e15

... (truncated)

Changelog

Sourced from rollup-plugin-ts's changelog.

2.0.4 (2021-11-19)

Bug Fixes

• regression in v2.0.3 on TypeScript <= 3.7 where ExportDeclarations could be dropped (f56c91c)

2.0.3 (2021-11-18)

Bug Fixes

• group ExportDeclarations by not just module specifiers but also whether or not they or their individual ExportSpecifiers are 'isTypeOnly'. Fixes #153 (493014c)

2.0.2 (2021-11-17)

Features

• add TypeScript v4.5 support (dffc8b7)

2.0.1 (2021-11-17)

Bug Fixes

• fix a problem with resolving swc configs (677c928)

2.0.0 (2021-11-16)

Bug Fixes

• add support for shimming regenerator-runtime when using swc as a transpiler (1513fc5)
• ensure that the drive letter is prefixed to absolute paths on Windows when getSourceFile is called internally from TypeScript (f368af3)
• ensure that the drive letter is prefixed to absolute paths on Windows when getSourceFile is called internally from TypeScript (cf6d3cc)
• when emiting declarations, always use define for class fields to work around limitations introduced in TypeScript 4.3 for when bundling declarations when a subclass overrides a property from the parent class but doesn't provide an initializer (b25a494)

Features

• add support for swc as a transpiler as an alternative to babel. #155 (e84d21c)

... (truncated)

Commits

• 3abd57e 2.0.4
• f56c91c fix: regression in v2.0.3 on TypeScript <= 3.7 where ExportDeclarations could...
• 78bb9a1 2.0.3
• 493014c fix: group ExportDeclarations by not just module specifiers but also whether ...
• 6821ee0 test: fix custom transformers test and run tests on TypeScript v4.4.2 as well
• 4745105 2.0.2
• dffc8b7 feat: add TypeScript v4.5 support
• 59c0415 2.0.1
• 677c928 fix: fix a problem with resolving swc configs
• c791d88 docs: documented how to opt out of @​babel-preset-env
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)