Charles Pick

> Here's another thought: we could have a preprocessing program go through all the type imports, and generate a file with all those types converted to validators if they aren't...

hey, thanks! Yes I'm absolutely interested in this, so right now you can do stuff like this: ```js import t, {reify} from 'flow-runtime'; import type {Type} from 'flow-runtime'; type User...

@mxstbr this doesn't already exist but a webpack loader is definitely something I want, it'd solve a lot of the problems we have that come from babel's single-file-at-a-time approach.

We're not yet using flow's config file and we aren't yet importing types from external definition files. We have a lot of the machinery in place - there's a concept...

@jamsea I just published v0.1.0 which should not throw in this case, just emit a warning. It should help in the interim. If you get sick of the warnings you...

in 0.3.0 this is mostly done, there's now `flow-runtime-cli` which can generate definitions from flow files, next step is to discover `.flow` files too

This turns out to be due to this part - `((V) => $DeepShape) & ((V) => V)` - which is an intersection of two functions. I was surprised to see...

The best fix for this is via a custom webpack loader / plugin I think, we just need more information than a file-by-file approach can give us

option 3 sounds like it would be the easiest to do, ```js // flow-runtime no-convert import {Baz, type Foo} from 'bar' ``` should produce ```js import {Baz} from 'bar'; const...

Glad to hear you like the library! For class invariants, it's doable but there are some limitations, e.g. the invariant won't be picked up by methods in subclasses, and I'm...