Please let me know if I am wrong, but I am not entirely sure we should include nodemon in the default start script as that script will be used by Heroku — which, I believe, has its own process manager. Nodemon is a dev tool and I'd argue it belongs in devDependencies. In that case, we'd use nodemon in a start:dev script or similar, which the main dev script would use (instead of start).
Usage in less automatic platforms, e.g. Digital Ocean, would then use something like pm2 to manage the server instance.
Following a conversation begun in #12.
Please let me know if I am wrong, but I am not entirely sure we should include
nodemon
in the defaultstart
script as that script will be used by Heroku — which, I believe, has its own process manager. Nodemon is a dev tool and I'd argue it belongs indevDependencies
. In that case, we'd use nodemon in astart:dev
script or similar, which the maindev
script would use (instead ofstart
).Usage in less automatic platforms, e.g. Digital Ocean, would then use something like
pm2
to manage the server instance.