Default import syntax doesn't work, but { default as } does.

[rdsedmundo]

Hello, look at the following please:

This results in a compile error:

import API from 'apifn';

// TS2351: Cannot use 'new' with an expression whose type lacks a call or construct signature.
export default new API('https://google.com', []);

This works:

import { default as API } from 'apifn';

export default new API('https://google.com', []);

Both allowSyntheticDefaultImports and esModuleInterop are set to true here.

I can't understand how those syntaxes are different, as I believe the default import syntax is part of the TC39 standard already or isn't it? Asking because this works perfectly with Babel. Only when I'm with projects with TypeScript that this confusion with default starts to happen.

The apifn package is a small package developed by myself. It uses TypeScript for generating ES5+Common JS.

Related Issues: #21621 (I originally posted there, but it was informed that they aren't related)

[Jessidhia]

This sounds like the problem and workaround I identified in #24528 (comment). Maybe it's fixed in @next.

[rdsedmundo]

Indeed they look related. I'll try with the @next version and let you know the results.

[rdsedmundo]

Yes, it's fixed by typescript@next.

Thank you.