Read the statement by Michael Teeuw here.
MMM-CalendarExt3 issue Loading / Showing the calendar on Windows
-
@sdetweil
just finished the install using cmd- made sure to install the fonts and vendor parts
- as well as change the package.json file and then did run start.
but it still did the same thing as before.
-
C:\MagicMirror>npm start > magicmirror@2.26.0 start > .\node_modules\.bin\electron js\electron.js C:\MagicMirror>
-
@JackHammer325 no .\ in front
the doc is wrong. windows doesn’t like . for current directory
-
@sdetweil
this is what i have in my package.json file. I removed the “.” like you recommended.
now i get “the system cannot find the path specified”
C:\MagicMirror>npm start > magicmirror@2.26.0 start > \node_modules\.bin\electron js\electron.js The system cannot find the path specified. C:\MagicMirror>
-
@JackHammer325 you only removed the dot I said no .\
so remove the slashes too
"node_modules\\.bin\\....",
-
@sdetweil
sorry guess i didn’t realize.
I’ve done that and it looks like it’s trying to start but then just goes back to this.C:\MagicMirror>npm start > magicmirror@2.26.0 start > node_modules\.bin\electron js\electron.js → sits here for about 8-10 seconds then does that ↓ C:\MagicMirror>
-
@JackHammer325 said in MMM-CalendarExt3 issue Loading / Showing the calendar on Windows:
TypeError: original.map(…).toSorted is not a function
Sorry for the late reply.
This error message is caused by using an old browser or not supported.
If you are usingChrome
orChromium
, it’s version should be newer than v110( - released, 2023-02-07, Current version is v120). Or for other browser, See above picture. -
@JackHammer325 said in MMM-CalendarExt3 issue Loading / Showing the calendar on Windows:
windows 8.1
yeh, missed that… That’s why the old browset
-
@sdetweil
I was happy to use a new featuretoSorted
but ppl may have trouble with compatibility issue. I’ll provide fallback codes in the next update. -
@MMRIZE we have this problem in general… mm used to display on TV’s and ipads/ android tablets… but as we’ve moved to ES6 level js, they no longer work… I find this a sad state for MM… (but I like the new ES6 support)