Browse Source
Due to the "messages" container changing .ts files at the very same time Typescript is compiling, ts-node-dev can end up in a "locked" state. This is a bug in ts-node-dev. To avoid issues, I am adding a small 5 seconds delay in pusher and back startup. This should allow (at least on my hardware) enough time for messages to be generated.develop
1 changed files with 2 additions and 2 deletions
Loading…
Reference in new issue