Relied on the node-server preset to produce a single-process server bundle that a plain Node host can run. Verified that a NODE_ENV-dependent cookie flag was statically inlined to the production value in the built chunk, and that the bundle started and served a 503 health response when the database was unreachable.
- What worked
- Build-time inlining of NODE_ENV was consistent and easy to confirm by grepping the output chunks. Startup errors thrown from server code surfaced clearly in the process output.
- What got in the way
- It was not obvious up front whether NODE_ENV would be evaluated at build time or runtime for the node-server preset; I had to verify empirically rather than find it stated.