Read the statement by Michael Teeuw here.
Can you help me about this error
-
-
I’d like to see any errors from your terminal and/or your console
-
@justjim1220
info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@3.10.10
3 info using node@v6.13.1
4 verbose stack Error: ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
4 verbose stack at Error (native)
5 verbose cwd /home/pi/MagicMirror/modules
6 error Linux 4.9.59-v7+
7 error argv “/usr/bin/node” “/usr/bin/npm” “start”
8 error node v6.13.1
9 error npm v3.10.10
10 error path /home/pi/MagicMirror/modules/package.json
11 error code ENOENT
12 error errno -2
13 error syscall open
14 error enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
15 error enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
15 error enoent This is most likely not a problem with npm itself
15 error enoent and is related to npm not being able to find a file.
16 verbose exit [ -2, true ]this is my npm-debug.log
i dont understand it i think its a problem with package .js
i try to start with npm start -dev for a error log
where is the error log in wich folder?thanks for your help
-
This is after only 15 min of MM running
-
@fonfon
One of your modules is usingpromise pattern
but not handling rejection. Usually this is caused by missing some exception handling in module.
I cannot figure out which module is causing that message. You can find which module has problem by disabling or removing module fromconfig.js
one-by-one.
Maybe your suspicious module might haveSOMETHING.hash
in its codes. the error will be caused objectSOMETHING
is reallynull
. so, when you find which module has the error, tell the module developer the symptom. (S)he will fix it. -
@fonfon
And one more thing.
Most of thoseUnhandledPromiseRejectionWarning
does not give harm to MM’s execution, the real problem isTypeError: Cannot read property 'hash' of null
. You should find which module is causing this message. -
@fonfon said in Can you help me about this error:
i try to start with npm start -dev for a error log
where is the error log in wich folder?Start MM with
npm start dev
. This opens the Developers Tools window. Click “Console” tab at the top of the window. Here you will find any errors. It does not save as a log.Follow Sean’s suggestion (and mine) that you determine which module is causing the issue. Then paste the errors from that module here.
-
@mykle1 When i start with npm start dev:
-
Do you get that error with just the default modules?
-
@mykle1 yes with default modules