Closed CMCDragonkai closed 5 years ago
This happens when you install any package or change the Flow config file. It is by design.
You can simply run yarn flow server
again to spin up a new server, or
rely on the server implicitly started by the next yarn flow
command.
Why is this by design? Can flow server not adapt to installing new packages?
ideally, agreed that it should adapt. but it's roughly an equivalent amount of work to restart than to recheck everything, and less error prone to just start over. the next request will restart the server. for now, this is by design.
Using
0.57.3
when runningflow server
. And then on another terminal runningnpm install --save kbpgp
results in this log: