Handle unresolved JS import when type is exported with the same name

[Coobaha]

This was not giving any error

// fileA.js
export type MyType = {};

// fileB.js
import { MyType } from './fileA.js' 

P.S. Some specs are failing in master?

1) ExportMap does not return a cached copy after modification:
2) exports-last valid
        const foo = 'bar'
        export default function foo () {
          const very = 'multiline'
        }
        export const bar = true
      :

[ljharb]

Overall this seems reasonable.

[ljharb]

This should probably use a template literal

[ljharb]

Maybe captureDoc should set the exportKind?

[benmosher]

There have been enough Flow issues lately that I'm tempted to have ExportMap just ignore them completely, especially since Flow will complain if things are wrong... but if the merge conflicts resolve without test issues, I'll probably merge as-is for now. Thanks!

[ljharb]

@Coobaha i've rebased this, and around 10 tests are failing. When i comment out your implementation changes, only 2 tests are failing.

I know it's been awhile, but it'd be great to get this updated and landed :-) please mark it as ready for review once it's so.

[ljharb]

@Coobaha im not sure why you deleted the branch; it’d be great to get this in. Can you restore and reopen it?

[Coobaha]

@ljharb Sorry was doing github cleanup and pruning stale branches. Branch is now restored