Flow: Flow 0.23.0 crashes with fatal error: End_of_file when an [include] folder is missing

Created on 20 Apr 2016 · 6Comments · Source: facebook/flow

Minor issue, but seems like it at least shouldn't crash. The end of the log says Fatal error: End_of_file

Crash bug

Source

jedwards1211

👍4

Most helpful comment

This also happens when we have this configuration .flowconfig:

[options]
module.system.node.resolve_dirname=node_modules
module.system.node.resolve_dirname=src

And you've just changed branches so that packages.json does not match what's in node_modules. Solution is npm install again.

haf on 24 Jan 2017

👍2

All 6 comments

I see there are a lot of closed issues relating to this error where further information couldn't be provided... The symptom seems random- in my case it appears due to some combination of async functions and ES6 import statements. Wish I could tell you more but as per everyone else's issues getting an exact test case together is pretty difficult...

pospi on 3 Nov 2016

This also happens when we have this configuration .flowconfig:

[options]
module.system.node.resolve_dirname=node_modules
module.system.node.resolve_dirname=src

And you've just changed branches so that packages.json does not match what's in node_modules. Solution is npm install again.

haf on 24 Jan 2017

👍2

@haf I ran into this with this exact configuration

capaj on 20 Feb 2017

I still get end_of_file exception failures. any update on this fix?

imoby on 1 Apr 2017

@imoby I had this same error today. Reinstalling the flow package (technically updating flow-bin from 0.42.0 to 0.44.2) using yarn add --dev flow-bin fixed the issue.

Edit: For completeness sake, I also noticed that my package.json file was missing the newline at the end, which got added in when I did the flow update.