![Auto import suggests different paths based on if any import is exported in parent index.ts · Issue #46753 · microsoft/TypeScript · GitHub Auto import suggests different paths based on if any import is exported in parent index.ts · Issue #46753 · microsoft/TypeScript · GitHub](https://user-images.githubusercontent.com/5993909/140967810-1d4dc5e7-c0e4-4059-a3ca-1e6b48a1a06a.png)
Auto import suggests different paths based on if any import is exported in parent index.ts · Issue #46753 · microsoft/TypeScript · GitHub
![JS intellisense does not work when d.ts contains import or export · Issue #17093 · microsoft/TypeScript · GitHub JS intellisense does not work when d.ts contains import or export · Issue #17093 · microsoft/TypeScript · GitHub](https://user-images.githubusercontent.com/1042507/28078170-2db9f400-668e-11e7-9480-48eeaf017603.png)
JS intellisense does not work when d.ts contains import or export · Issue #17093 · microsoft/TypeScript · GitHub
Interface merge of import/local should error when the import is re-exported with `export *` · Issue #9532 · microsoft/TypeScript · GitHub
![reactjs - Why does typescript infer a default prop when we dynamically import a javascript file which does not have a default export - Stack Overflow reactjs - Why does typescript infer a default prop when we dynamically import a javascript file which does not have a default export - Stack Overflow](https://i.stack.imgur.com/qWjqz.png)
reactjs - Why does typescript infer a default prop when we dynamically import a javascript file which does not have a default export - Stack Overflow
![typescript: export type MyType "is not exported by a module". · Issue #3351 · rollup/rollup · GitHub typescript: export type MyType "is not exported by a module". · Issue #3351 · rollup/rollup · GitHub](https://user-images.githubusercontent.com/7501201/72786494-c6d97380-3c3e-11ea-998a-238ddb994c0b.png)