Read the statement by Michael Teeuw here.
Debugging
-
I suspect the answer is: go read the source code … but, what are you trying to do?
-
It’s my source code :laughing: - My object should have an available function to me, but it’s coming up function not found. I’m gonna keep digging! New module is on its way.
-
Theeeeen you’re not defining it as a function … ?
-
You don’t have to run the the code in the electron every time. I would just run “node index” from the /serveronly folder and start the chrome with dev tools on my dev box. Also as dev tool Visual Studio Code is a very good one and runs on Windows, Linux and OS X. You could configure it to debug the node.js as well as the chrome client (via a plugin) locally or even have a remote debugging session.
-
This post is deleted! -
I could not use
Log.log('foobar');in the node_helper.js and if i useconsole.log('foobar');the log is shown in the CLI. Is there a solution to show it in the Browser Console? -
@BenRoe quote from the readme
The Magic Mirror contains a convenience wrapper for logging. Currently, this logger is a simple proxy to the original console.log methods. But it might get additional features in the future. The Loggers is currently only available in the core module file (not in the node_helper).so everything you have experinced is as it should beinstead of logging in the node_helper directly you could send the string, objects, etc. to your module and use the logger there to view it in the browsers console
-
@strawberry-3.141 I got the following error when I run pm2 log mm:
error: cannot open .git/FETCH_HEAD: Permission denied
-
@Sputnik could be the updatenotification module, which is probably not able to read a modules git config. Did you download modules manually or did you use git clone?
