Flow Definitions Removed During Compile/Build about express-graphql

[ryyppy]

As of the state right now, there are only two ways to properly consume types from npm packages:

1. Either Convince the project maintainers to provide a build step to basically recursively copy all src/ files to dist/ to the same position as the ES5 files with a flow.js suffix (AFAIK draft.js will do this in the future)
2. Or create and consume a libdef file separately (as currently done in flow-typed)

Option 2 will also be required if you try to use an minified browser build of course, since in my knowledge there is no automated way to extract all types into a single file ...

For this project, Option 1 would actually be a good fit

[nodkz]

Also, you may track progress with graphql-js here graphql/graphql-js#359

[mwalkerwells]

Just found this: flow-typed/flow-typed#16

[mwalkerwells]

@leebyron Curious if #1 is something you'd consider?

[leebyron]

Yes, this is something I think is worth considering, though the graphql package itself should export types in the same fashion first.

It's also worth point out that the Flow team does not encourage libraries export types in this way due to possible breakage when Flow updates.

[mwalkerwells]

Ah, interesting—that makes sense.

[mwalkerwells]

Flow v32 Release Notes:

We're starting work on flow gen-flow-files, which consumes Flow code and outputs .flow files containing only the types exported. It's alpha-level and we're still iterating on it, so use at your own peril!

:)

[nodkz]

Yep, incredible synchronous work of Facebook's OSS teams.

Lee posted about flow 0.32 in tweeter yesterday.

[mwalkerwells]

Thanks—& yes, they're OTS.