Read the statement by Michael Teeuw here.
MMM-LogExt
-
MMM-LogExt
Log Extension module for MagicMirror
Concept
Many beginners have a problem tracing an unexpected issue when they run the MagicMirror.
Usually, the start of debugging would be to examinebackend-log
andfrontend-log
but people may have confusing to use both how to.I know there already exists
MMM-Logging
to help with this issue, but it seems not maintained anymore, and I need more features, so I have to re-invent a wheel by myself.Features
- To deliver frontend log (used by MM’s
Log
Object) to backend log - Customizable/Decorative Log messages
- To monitor Notifications
window.error
andunhandledRejection
would be caught then be transmitted to the backend- To be able to log external messages from other programs or devices via HTTP request
IMPORTANT : This module deliver only
Log.xxx()
to the backend, notconsole.xxx()
. - To deliver frontend log (used by MM’s
-
@MMRIZE Curious - does this have any purpose other than prettying logs for PM2 users?
-
@BKeyport it merges the Dev window messages and the node_helper messages…
pm2 doesn’t see the developers window messages (from the modulename.js Log(…) function
-
@BKeyport
You can see the browser-side log in the backend (terminal or log file) without ‘npm run start:dev’ or dev-console of chromium.
Frankly said, I’m a bit tired with always saying “open your dev-console and let’s see whether there be suspicious errors,… no, that is element tab, console tab is another, you can see those tabs in upper right side,… first you should have stopped the pm before,…” :D