Importing a mix of types and values in an import using a custom path results in undefined imports in result JavaScript

Given:

file1.ts:

export type Foo = 'bar';

export const baz = 'inga'; // ;)

file2.ts:

import { Foo, baz } from '@custom/scope/file1';

[...]

When the code is compiled, the Javascript import will read something like this:

file2.js:

import { Foo, baz } from '@custom/scope/file1';

but Foo will be undefined and cause errors.

[booninite]

@danielpza I wasn’t able to pick up the fix today, I should be able to try it out tomorrow and can let you know 👍

[DmitryKoterov]

@danielpza Unfortunately PR #53 doesn’t help, still the same effect.

Here is a with minimal code which reproduces the issue: https://github.com/DmitryKoterov/typescript-transform-paths-bug - could you please take a look?

Those excess import symbols don’t allow to use es6 modules since node complains on an attempt to import an undefined symbol: