How to apply flow type checking in lerna managed project?

Since Lerna hoists common npm packages into root node_modules folder, running flow in each package cannot find these common npm packages in its own node_modules folder. It would fail with error message as below.

  5: import {createStore, applyMiddleware, combineReducers, compose} from 'redux';
                                                                          ^^^^^^^ redux. Required module not found

In above case, redux is hoisted to node_modules in root node_modules.

Is there any practice to workaround for flow type-checking?

[steelbrain]

@sibelius Relying on third party solutions is not ideal. While I agree this particular issue is out of scope for Lerna itself, I still think it should be taken care of in flow instead of some third party wrapper or fork

[mocheng]

@evocateur I checked @wtgtybhertgeghgtwtg 's repo and found the difference. In that repo, flow is run at root instead of each package. And, there is a flow-typed sub folder holding dependency package libdef.

Surely, we can leverage same strategy to make flow work in lerna. But, it is preferred to enable each sub-package could run flow independently without much setup.