Import wrongly elided with a combination of default export, named export, non-exported type

[Retsam]

Bug Report

🔎 Search Terms

import, elision, elided, default

🕗 Version & Regression Information

• This changed between versions 4.1.5 and 4.2.3

⏯ Playground Link

Workbench Repro

💻 Code

// @showEmit
import MyFunction from "./MyComponent";

MyFunction({msg: "Hello World"}); // Runtime error, MyFunction was not imported


// @filename: MyComponent.ts
interface MyFunction { msg: string; } // adding export here fixes

export const MyFunction = ({ msg }: MyFunction) => console.log(`Got message "${msg}"`); // removing export here fixes
export default MyFunction;

🙁 Actual behavior

The import MyFunction from "./MyComponent"; is elided from the output - causing the MyFunction(x) line to crash.

🙂 Expected behavior

Expected the import not to be elided since it is exporting a value, and the import is used as a value.

Alternatively, an error about this pattern of default export + named export + non-exported type would be helpful. This is a bizarre, accidental, export pattern, and it was an easy fix, but it was a bit tricky to track down. (We found this when switching a large codebase from babel compilation to TS compilation)

[tpluscode]

Here's a minimal repro showing this happen when using a @types package: https://gist.github.com/tpluscode/cbcd3f47b45f719475e079dd76801344