I don't know the best package for logging in standard JS projects, but I know to use logger.info(), logger.debug(), logger.error() is standard in all logging frameworks across languages.
Simple.Logger showed up as the most lightweight library to log to console.
So I replaced the console logs with appropriate logger levels, which means that if the package needs to be changed or something else happens later, it won't affect the code logger levels again.
I added some tracing around the network loop as I struggled to understand why it wasn't finding the IP address for MAC
I don't know the best package for logging in standard JS projects, but I know to use logger.info(), logger.debug(), logger.error() is standard in all logging frameworks across languages.
Simple.Logger showed up as the most lightweight library to log to console.
So I replaced the console logs with appropriate logger levels, which means that if the package needs to be changed or something else happens later, it won't affect the code logger levels again.
I added some tracing around the network loop as I struggled to understand why it wasn't finding the IP address for MAC
Refers to issues https://github.com/daniela-hase/onvif-server/issues/2 and https://github.com/daniela-hase/onvif-server/issues/3