MMM-Worldclock

JohnGalt

@BKeyport, @ulrichwisser and all: Please let me know if the following questions would be better served under a new topic, but since my issues originated with this older module, and the new module shares the same name I thought it appropriate to post under this topic…

Issue: the old module is no longer supported by the developer, who suggests using a newer module which uses the same module name. After cloning the new module, the instructions call for doing an ‘npm ci’ command, which fails due to a lack of an existing package-lock,json file.

Question: Is there something different I should be doing, o si this something the developer needs to fix?

Old module: https://github.com/BKeyport/MMM-Worldclock
New module: https://github.com/ulrichwisser/MMM-Worldclock
Error Message:

pi@mirror1:~/MagicMirror/modules $ cd MMM-Worldclock
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm ERR! [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm ERR! [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info

npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-05T17_16_59_150Z-debug-0.log
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $

sdetweil

@JohnGalt npm install then

JohnGalt

@sdetweil – That’s what I thought. Just did that and it’s working now…

Thanks, as always!

BKeyport

My version of the module developed a fatal bug that I couldn’t get rid of… The best move was to shut it down.

JohnGalt

@BKeyport – Sorry to hear that, but thanks for the module while you maintained it.

And a big thanks for directing us to another module, and not just leaving it hanging out there!

UncleRoger

@BKeyport
Was the altflag option something that was related to the fatal bug in your version? If not, do you think it’s something that could be added to the latest one?

BKeyport

@UncleRoger No, it wasn’t that. I forgot about that code. I might go back in and grab it and offer it to the other version once updated.