You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know that all stubs fail to type check, but a healthy amount of them seem to. This might warrant tracking as multiple tickets but I wanted to start from somewhere.
Here's my setup:
flow 0.75
flow-typed 2.5.0
I run yarn flow-typed install and expect there to be some stubs generated. The command completes successfully. I restart the flow server and these are the errors I see:
There's a smattering of issues that I can see from glazing over the errors:
Stubs generated from JSON files need to have their identifiers quoted (see max-len-2 for an example).
It looks like we're trying to generate CommonJS exports from ES6 modules. As a result we're exporting an object with a default that has no key on the object, and this isn't valid syntax. This is seen at the start of most of the erroneous modules listed above.
Some of the identifiers are actual keywords so they fail to parse. There's an example of "Unexpected token default". It might mean I'm wrong about the CommonJS/ES6 module mismatch on my item above. Since we're generating these identifiers it might be prudent to just quote everything pessimistically.
The text was updated successfully, but these errors were encountered:
I don't know that all stubs fail to type check, but a healthy amount of them seem to. This might warrant tracking as multiple tickets but I wanted to start from somewhere.
Here's my setup:
I run
yarn flow-typed install
and expect there to be some stubs generated. The command completes successfully. I restart theflow
server and these are the errors I see:There's a smattering of issues that I can see from glazing over the errors:
max-len-2
for an example).default
that has no key on the object, and this isn't valid syntax. This is seen at the start of most of the erroneous modules listed above.The text was updated successfully, but these errors were encountered: