Easy way to restart/refresh flow server

[IanLondon]

Thank you for this amazing tool!

I noticed that sometimes when I change file directory structures or .flowconfig settings, both node_modules/.bin/flow and also the errors from ide-flowtype haven't refreshed to look at the new paths/files/etc.

From the console I do node_modules/.bin/flow stop then I hit Ctrl + S in Atom to force ide-flowtype to start a new server and re-check the file. If I have a lot of tabs open, I have to Ctrl + S over all the open files to update them.

Is there an easier way to do this? If not, an option to "Restart Flow Server and Refresh all Files" to the Atom command palette would be helpful.

Thanks!

[rhysforyou]

This might be an entirely separate issue, but I often encounter an issue where I'll open a newly 'bootstrapped' JS project in Atom, and then later run npm i -D flow-bin && flow init from the command line. In that case, I have to fully quit out of and reopen Atom for it to pick these changes up.

[mattcollier]

@IanLondon I would seem the flow server is getting jammed up for a variety of reasons atm. I have found that Ctrl+Shift+F5 a.k.a. View->Developer->Reload Window does the trick for me on Linux.

[saadq]

This issue seems to happen for me mainly when I change the .flowconfig file or if I manually edit a library definition in the flow-typed directory. Doing the Reload Window command is the easiest way to get Flow running again, but it gets a bit annoying.

[vonwao]

what is Reload Window command? I don't know what you're talking about

[saadq]

In Atom, you can open up the command palette with command+shift+P (or ctrl+shift+P if you're on Windows/Linux), and then type in Window: Reload, and press Enter. Alternatively, you can do it from the menu bar at the top:

[jedwards1211]

@wbinnssmith I imagine Facebook isn't really giving you as much time as you deserve to work on ide-flowtype, are they?