Cannot find module 'node-fetch' error with MMM-SoccerLiveScore

[codac]

@karsten13

docker run

[codac]

@sdetweil
This error only comes up when trying to restart MM inside the docker.
When restarting the docker, this error wont show up.

[codac]

@karsten13
This is a server only setup. Docker runs on “Container Manager” of Synology. The Synology is a DS420+ running on an INTEL Celeron J4025. The OS is DSM of course.

[karsten13]

@codac

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

[codac]

@karsten13 WebUI

[sdetweil]

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

[karsten13]

@codac

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

[karsten13]

@sdetweil

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

[codac]

@karsten13 well restarting / stopping / starting is no problem. But the error just remains and doesnt go away…

[sdetweil]

@codac which error? the node-fetch or the lib error?

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

[codac]

@sdetweil the node-fetch error

[karsten13]

@codac

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)

[sdetweil]

@karsten13 did they fix the module? I didn’t check

[karsten13]

@sdetweil

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

[KristjanESPERANTO]

I created a PR to fix this, let’s see when @0m4r accept it.

[sdetweil]

@KristjanESPERANTO well, npm install would have installed the devDependencies too…

[KristjanESPERANTO]

@sdetweil Sure. But my PR removes node-fetch, so npm install is no longer necessary for this module.

[karsten13]

@sdetweil

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

[codac]

@karsten13
@codac said in Cannot find module 'node-fetch' error with MMM-SoccerLiveScore:

@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   

[codac]

@karsten13 said in Cannot find module 'node-fetch' error with MMM-SoccerLiveScore:

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.