Module dependency graph for reloading

[orta]

This is something handled by a Haste Map in Jest.

That said - flow does have something for this:

npm run flow -- get-imports app/containers/artist/index.js

> relational-theory@0.0.1 flow /Users/orta/dev/js/apps/relational-theory
> flow "get-imports" "app/containers/artist/index.js"

Imports for module 'app/containers/artist/index.js':
	/Users/orta/dev/js/apps/relational-theory/data/graphql-export.flow.js@/Users/orta/dev/js/apps/relational-theory/app/containers/artist/index.js:6:33,6:67
	/Users/orta/dev/js/apps/relational-theory/app/containers/artist/components/header.js@/Users/orta/dev/js/apps/relational-theory/app/containers/artist/index.js:5:26,5:46
	react-relay@/Users/orta/dev/js/apps/relational-theory/app/containers/artist/index.js:4:19,4:31
	react@/Users/orta/dev/js/apps/relational-theory/app/containers/artist/index.js:13:7,13:11

[orta]

And flow is compiled to JS as a npm module, so you may be able to do ^ without the process call - not 100% on that

[orta]

This above only works if you have @flow in every file, which I have a branch of now

[orta]

orta@b3140ad

[alloy]

Dope. Normally I’d probably go for using Jest’s HasteMap because it probably has less dependencies than flow, but we already depend on both, they’re only needed in development, and the API seems complicated whereas maybe Flow’s is simple? Let’s go with whichever of the two has the simplest API and less impact in our source.

[alloy]

PS I assume you’ll PR that flow branch?

[orta]

yes

[orta]

soon

[alloy]

Closing this in response to #10.