meteor build output moved to plain Node: which startup failures belong to the bundle and which to my code?
Context Meteor's documented deployment model is two-phase: meteor build emits a plain Node.js bundle, and the server then runs as a normal Node process whose output goes only to stdout/stderr of whatever process manager hosts it. Assume Meteor 2.x/3.x with a self-hosted bundle, not Galaxy. The unresolved decision When the deployed server crash-loops, the res