Imported npm package throws errors within flow about graphql-js HOT 5 CLOSED

Here is a quick fix if you want to continue to work before that issue gets fixed:

Add this to your .flowconfig:

[ignore]
.*/node_modules/graphql/lib/.*

EDIT Nope, it doesn't work. The imported module won't exist anymore for flow...

EDIT2 Add this to your Makefile or in a package.json hook or anything you want to use:

cd node_modules/graphql && find . -type f -print0 | xargs -0 sed -i '' 's/@flow//g'

This will strip the @flow from the GraphQL-js's files. Take this as a temporary solution.

from graphql-js.

Sorry about this. I will bring this up with the Flow team to get their best advice

from graphql-js.

Oh don't worry! I deactivated the error with my small sed regex. It will be
fixed when it needs to be. Thanks for bringing this up to the flow team on
this though! Again, I can write the patch if it's not top priority for you
at fb.

On Mon, Jul 6, 2015, 03:28 Lee Byron [email protected] wrote:

Sorry about this. I will bring this up with the Flow team to get their
best advice

—
Reply to this email directly or view it on GitHub
#25 (comment).

from graphql-js.

With the recent change to babel, the /*@flow*/ header is now removed, so hopefully this solves your issues.

I'll continue to look into nicer ways to improve this going forward.

from graphql-js.

It would be briliant to have flow annotations preserved. For instance in facebook/draft-js they leave the original code in /lib/ and place the generated plain javascript in /build/.

from graphql-js.