Read the statement by Michael Teeuw here.
Debugging
-
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.
-
Hi,
I’m trying to dev a module too and I’m trying to debug too. Sadly I get a white screen, like when the config file is incorrect. I’m pretty sure the config file is OK, because the only thing I add is
{ module: 'MMM-Ratp', position: 'top_right' },
Where MMM-Ratp is the name of my module.
I tried to use the console (I’m using firefox) and it works fine when MM is running, but when I get a white screen under Epifany webbrowser (default one), under Firefox, I get “Unable to connect” like if the web server was not running so I don’t have any log and I don’t know whether it is a code error in my plugin, or something more stupid like denied access to one specific file or anything else I forgot like registering the module
I then did a test with a Helloword plugin, it works fine. Then I copy the HW code to my plugin.js, just renaming the file and then it’s not working. I thought that the issue would be an access denied but doing ls -al (I’m noob with linux), the chmod seem to be the same for both plugin (read access)
Any idea where to start digging ? thx
[edit] I’m moving forward. it was because as soon as placed in the module folder, the node_helper seems to be parsed and executed and I had some modules required which were not installed. Now, the module is loaded but not working. I continue digging :)
-
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?