NODE_ENV=test npm install node-fetch@2

I could see that this time node-fetch got installed (different than before running npm install node-fetch@2 only).
But after restarting the docker container, the same error remained.

Thank you guys for your massive support. Big time!
@karsten13, @sdetweil, @KristjanESPERANTO

NODE_ENV=test npm install node-fetch@2

I could see that this time node-fetch got installed (different than before running npm install node-fetch@2 only).
But after restarting the docker container, the same error remained.

@sdetweil

root@04492d039b9f:/opt/magic_mirror/modules# cd MMM-SoccerLiveScore              
root@04492d039b9f:/opt/magic_mirror/modules/MMM-SoccerLiveScore# npm install node
-fetch@2                                                                         
                                                                                 
up to date, audited 1 package in 1s                                              
                                                                                 
found 0 vulnerabilities                                                         

How would I restart MM of the container?
pm2 is not set up.

DISPLAY=:0 npm restart

…results in

> magicmirror@2.26.0 restart                                                     
> npm stop --if-present && npm start                                             
                                                                                 
                                                                                 
> magicmirror@2.26.0 start                                                       
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js           
                                                                                 
sh: 1: ./node_modules/.bin/electron: not found   

well, npm install would have installed the devDependencies too…

This sentence clicked in my brain.

I have NODE_ENV=production as default in my images (expect images I use for testing) and with this

• npm install will install nothing
• npm install node-fetch@2 will install nothing

so @codac please go again in the folder of the module and run NODE_ENV=test npm install node-fetch@2

this should hopefully solve the issue

you are right, they “fixed” it in devDependencies instead in dependencies …

then git pull is useless, you have to install the missing library in the module folder as sam already explained above

if you are using https://github.com/0m4r/MMM-SoccerLiveScore the module contains the missing node-fetch so you should do a git pull in the module folder and try again (which means restart the container)

(@karsten13 we installed electron, my mistake… in docker, doah! )

and I think the electron error is just noise, as you must be running server only mode, whcih doesn’t use electron

yes, there is no electron installed

I don’t know this WebUI, you have to restart the container or stop and start again, whatever the WebUI provides

and how do you start/stop the container? With a WebUI or per command line?

docker run

I don’t now, the old electron process is still running

but we now nothing, how he started, in server only or with electron, which architecture, which host os, which hardware …