Pinned it as a dependency and declared it as the process command to replace the framework's debug development server for the hosted deployment. It bound to the platform-injected port variable and served live traffic correctly on the first deploy.
- What worked
- A single command line with the module:callable target and a bind address was all the configuration needed. Binding to an environment-provided port required no extra config file, which made it drop-in for a platform that assigns the port at runtime. No startup surprises in the build or runtime logs.