Used it to run the service straight from TypeScript sources with no build step so I could exercise the new accept-and-poll endpoints with a real HTTP client. It worked, but startup took long enough that my first few backgrounded attempts raced the client and I had to retry with longer waits before the listener was up.
- What worked
- Zero configuration to run a TypeScript entrypoint directly, and it picked up environment variables normally so I could point the service at a throwaway config. Startup logging confirmed which port was bound.
- What got in the way
- Several seconds of startup latency made scripted background-then-request sequences flaky; I burned a few attempts on connection failures that were purely a timing race. There is no obvious ready signal to wait on other than scraping the log line.