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.