npm start dev

[shavesophere]

Thanks ost - but I have tried it both from direct physical keyboard and SSH using this command. I’ve been reading a few other problems related to this issue but all seems to come down to “not installing as root user”. Which i’m not - I’m installing as pi. So still scratching my head here.

[ostfilinchen]

do you have create an mm.sh and starts this with pm2?

[shavesophere]

@ostfilinchen I was just using the standard install script that comes on the tutorial.

curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh | bash

[ostfilinchen]

and do u do these steps: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

[Bangee]

hey there
@ostfilinchen that’s it. to start npm from my shell it need to use this command:
DISPLAY=:0 npm start dev

But with this I can not debug my script. Electron crashes alwasy on startup when I’ve activated my new module using const sensorLib = require('node-dht-sensor') in my node_helper.js

How can I debug this error?

[shavesophere]

OK i think i’ve solved it. magic mirror HAS to be started (npm start) from a terminal window in the x-window server. you cannot start it over ssh.

[bhepler]

@shavesophere Thank you. This at least got me to the point where I can show the display on a monitor. Now I just have to walk to the other room to see my changes. :/

[KirAsh4]

@shavesophere said in npm start dev:

OK i think i’ve solved it. magic mirror HAS to be started (npm start) from a terminal window in the x-window server. you cannot start it over ssh.

Not true. It can be started over SSH just fine: DISPLAY=:0 npm start

[shavesophere]

@KirAsh4 sorry - i stand corrected! but that being said when i first started getting npm ERRS i tried this and it still did not work… anyway, moving forward now!

[KirAsh4]

@shavesophere said in npm start dev:

@KirAsh4 sorry - i stand corrected! but that being said when i first started getting npm ERRS i tried this and it still did not work… anyway, moving forward now!

Well yeah, that’s different. If npm is giving you errors, no matter how you attempt to start it, the errors won’t magically go away. That’s like saying, the car won’t start if I’m sitting on the left side, maybe if I sit on the right side it might, but in reality there’s no gas in it. Switching seats isn’t going to fill the gas tank. :)