NodeJS API changes not reflected on remote development target

For a target setup:

Remote
Node w/apache proxy
Development
PM2

Changes to Content pages are immediately reflected.

Changes to API’s are not available until I restart the node server.

If I use --watch on PM2, then the API changes trigger a restart, but for Content pages it restarts the server twice (nodemon is doing one, and then PM2 is doing one.)

@patrick @George What is the proper config when using PM2 to manage multiple sites on one server? Is this just a bug on the restart.txt of API files?