Releases: wessberg/rollup-plugin-ts
v1.3.3
v1.3.2
v1.3.1
v1.3.0
Bug fixes
- fix(external): respect 'external' option provided to Rollup and don't inline typings from modules matched by it 06f453a
Breaking Changes
Previously, the external option you provided to Rollup as part of your config was ignored by rollup-plugin-ts. Instead, it had internal rules for deciding whether or not to inline typings from imported modules or not based on things like whether they originate from external libraries. This could cause issues in complex scenarios combining TypeScript project references with tools like Lerna.
Going forward, just like Rollup, rollup-plugin-ts will respect the external option and leave imports be if they are matched by it.
For example, if your code looks like this:
// is path mapped to "@some/package/src/index.ts"
import {Foo} from "@some/package";and your Rollup config looks like this:
{
// ...
external: ["@some/package"]
// ...
}Then the import will be left alone, rather than inlined. This follows the conventions of Rollup.
This probably won't affect you unless you are doing complex path mapping with TypeScript project references and symlinking.
v1.2.34
v1.2.33
v1.2.32
v1.2.31
v1.2.30
Bug Fixes
- fix(babel): babel configs cannot be resolved correctly. Closes #101. Closes #95 044588e
v1.2.29...v1.2.30
Breaking Changes
Previously, if you provided inlined babel options, the plugin would use only them and force Babel to not search for any other config files based on your options. This theoretically makes sense in situations where you want to bypass searching for a config file on desk and instead provide the options directly. However, this is not how Babel is designed to operate. Going forward, inlined babel options will be combined with those that can be resolved, as is the way Babel normally works. This means that you can now provide things like rootMode as a Babel option, and it will actually work as expected:
{
plugins: [
// ...
ts({
transpiler: "babel",
babelConfig: {
// Any babel options go here
rootMode: "upward"
}
})
]
}If you want to instruct Babel to bypass searching for a babel config on desk altogether (such that you get the old behavior), provide configFile: false and/or babelrc: false as Babel config options:
{
plugins: [
// ...
ts({
transpiler: "babel",
babelConfig: {
// Explicitly tell Babel that it shouldn't look for other Babel configs to combine with these options
configFile: false,
babelrc: false
}
})
]
}