michaelm

cc @ahejlsberg since you made some significant type flow analysis changes

I looked a bit into what part of https://github.com/microsoft/TypeScript/commit/162713fac9da0304769ef0b7cfdd568f319a55ea caused this regression. It seems like adding `isEntityNameExpression(expr.argumentExpression)` to `isNarrowableReference` allows `flowNode`s to be set on expressions where they weren't previously...

@bnjmnt4n @falsyvalues Any chance that this can be released in a patch version? This is a pretty glaring bug as you can see from the added test cases and could...

Hi @mathiasbynens, do you have merge + release privileges? My company, and I'm sure others', doesn't want to have to maintain a patch of lodash and migrating away is not...

@bnjmnt4n @falsyvalues @jdalton @jridgewell @JSFOwner @veksen @zackhall ping

@Andarist you've been pretty capable at fixing random bugs I've stumbled upon before, so maybe this one would be of interest to you 😉

That's fair. An idea I haven't put much thought into is to emit something like ```ts export enum Foo { A = 1, B = 2, } export declare const...

Subtle, didn't realize unique symbols had such _unique_ behavior 🙂

@dragomirtitian I think I found a false negative, a case that should error but doesn't. `mapping` should report an error here. Interestingly, the `ts.transpileDeclaration` API does detect the error. There...

I believe this is blocked by https://github.com/benjamn/ast-types/issues/343