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
Now I'm down to a mere 1228 files checked. flow status runs dramatically faster: 0.5s instead of 2.5s.
I suspect there are many Flow users who don't realize that they have a ton of node_modules slowing them down. Adding a less roundabout way to get at the number of file checked would encourage users to deal with this. One way would be to add a file count to the No errors! message.
The text was updated successfully, but these errors were encountered:
TL;DR: Instead of
No errors!
, Flow should say something likeNo errors! (Checked 1,234 files)
.I recently noticed that vim-flow was getting borderline annoyingly slow. Whenever I saved, it took ~3 seconds for me to get control of my cursor back.
I could reproduce this on the command line in my project:
I had 81 files in my repo and I was using Flow 0.16.0:
Eventually I discovered the reason that Flow was slow: it was scanning over a ton of irrelevant files in
node_modules
:I tried adding this to my
.flowrc
, but it produced many errors:I wound up using this command to find the worst offenders:
and I blacklisted them in my
.flowconfig
:Now I'm down to a mere 1228 files checked.
flow status
runs dramatically faster: 0.5s instead of 2.5s.I suspect there are many Flow users who don't realize that they have a ton of
node_modules
slowing them down. Adding a less roundabout way to get at the number of file checked would encourage users to deal with this. One way would be to add a file count to theNo errors!
message.The text was updated successfully, but these errors were encountered: