If this is a bug, please try reproducing using https://flow.org/try/.
As a first-time user of Flow, wasted a lot of time trying to figure out how to fix that error - when it turned out that all it means is that you need to install a type definition for the module. I thought it was having issues finding or importing the module itself.
Suggestion: "Cannot resolve module X. The module may not have typing definitions, which can be installed using flow-typed."
This. I'm also another one who wasted a lot of time and already made me a little demotivated to use flow
as it's being described as an easy-to-run tool and was actually very frustrating.
Or maybe I'm just misunderstanding something, but this does not seem to be a thing, because I get this error only on specific libraries (which apparently don't have the types as @toddmedema describes it).
I've wasted so much time on the flow-typed nonsense. Why cant I just ignore imports?!?!?! Configuring flow is a nightmare!
@moaiii You can ignore imports actually.
Flow is not nightmare at all. It's far from perfect, but it's absolutely usable even with Meteor, which has its own unusual magic.
Most helpful comment
This. I'm also another one who wasted a lot of time and already made me a little demotivated to use
flow
as it's being described as an easy-to-run tool and was actually very frustrating.Or maybe I'm just misunderstanding something, but this does not seem to be a thing, because I get this error only on specific libraries (which apparently don't have the types as @toddmedema describes it).