@kristjanesperanto what do you think of this?
Hmm… I didn’t expect something like that in the current release. But I won’t be able to take a closer look at it right away. It would be interesting to see if this also happens in the develop branch.
@kristjanesperanto what do you think of this?
Hmm… I didn’t expect something like that in the current release. But I won’t be able to take a closer look at it right away. It would be interesting to see if this also happens in the develop branch.
@angeliKITTYx thanks
@kristjanesperanto what do you think of this?
We’ve made sure to erase node_modules and start fresh
@angeliKITTYx ok, now start MagicMirror
@angeliKITTYx ok then, one more time
cd ~/MagicMirror
rm package-lock.json
rm -rf node_modules
npm run install-mm
@angeliKITTYx that means the install-mm did not work
Please do again and show the output
@angeliKITTYx looks like you didn’t do that in the MagicMirror folder
cd ~/MagicMirror
npm run install-mm
@kkmirr04 ext3 gets its events from the default c as lender module and can use the color definition there
Different for each url used/defined
Can you show your default cal Module config
Xxx out the urls
Did you get the npm run install-mm done after verifying node version was correct?
@TiLow just ignore the punycode message.
We are discussing ways to distribute a number of fixes
@angeliKITTYx awesome. Thanks for the feedback
package-lock? Erase that file then do the update
There is a known bug affecting modules that have functions in their config like ext3. We are discussing ways to distribute these fixes.