MMM-NewsFeedTicker.

[ankonaskiff17]

Is there a missing component in the MMM-NewsFeedTicker. I’ve installed it twice, one two different machines and it stopped MM in its tracks. Put in modules folder as required, copied config.js module block and put in config folder.
No settings changes, launched MM and got black screen. Pulled section of config.js back out, restarted, black screen.
Deleted MMM-NewsFeedTicker from modules folder. Everything back to normal.
Tried to launch dev tools but while window came up, there was an error message where normally would be css code, etc.

[sdetweil]

@ankonaskiff17 remember that we deleted old libraries in 2.16 , many modules didn’t document that they were needed, and SO, we end up with a crash

see the messages where u start MM, and look for ‘module not found’ and then npm install those in the MM folder …

probably one of

request
rrule-alt
valid-url

[greedyvegan]

@sdetweil said

request
rrule-alt
valid-url

this still doesn’t work

[sdetweil]

@greedyvegan show me the messages from mm npm start

[greedyvegan]

@sdetweil show me the message from npm start

after starting mm v2.26.0 it says
loading config…
[DEBUG] config template file not exists, no envsubst
loading module helpers…
no helper found… initializing new module helper
then…

[sdetweil]

@greedyvegan that says you have an instance running already, do

pm2 status

then

pm2 stop all

then

pm2 start  xx

xx is the number or name on the row

[greedyvegan]

@sdetweil
which row?

[sdetweil]

@greedyvegan share the output of
pm2 status

[greedyvegan]

@sdetweil
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ fork │ 29 │ stopped │ 0% │ 0b │
│ 2 │ mm │ fork │ 0 │ stopped │ 0% │ 0b │
│ 1 │ run-start │ fork │ 0 │ stopped │ 0% │ 0b │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

[sdetweil]

@greedyvegan hm…
run this

ps -ef | grep  MagicMirror  | awk '{print $2}` | xargs sudo kill  -9

the. try. npm start