MagicMirrorOrg/MagicMirror · warning

Version is incorrect. Skip module: '${name}'

Error message

Version is incorrect. Skip module: '${name}'

What it means

During Module.register, a module can declare requiresVersion. If the running MagicMirror version (window.mmVersion) compares lower than that minimum (cmpVersions < 0), registration is aborted with this warning and the module definition is never stored, so the module will not load.

Source

Thrown at js/module.js:501

				super();
				Object.assign(this, clonedDefinition);
				if (typeof this.init === "function") {
					this.init();
				}
			}
		}
	}[className];

	return new SubClass();
};

Module.register = function (name, moduleDefinition) {
	if (moduleDefinition.requiresVersion) {
		Log.log(`Check MagicMirror² version for module '${name}' - Minimum version:  ${moduleDefinition.requiresVersion} - Current version: ${window.mmVersion}`);
		if (cmpVersions(window.mmVersion, moduleDefinition.requiresVersion) >= 0) {
			Log.log("Version is ok!");
		} else {
			Log.warn(`Version is incorrect. Skip module: '${name}'`);
			return;
		}
	}
	Log.log(`Module registered: ${name}`);
	Module.definitions[name] = moduleDefinition;
};

/**
 * Compare two semantic version numbers and return the difference.
 * @param {string} a Version number a.
 * @param {string} b Version number b.
 * @returns {number} A positive number if a is larger than b, a negative
 * number if a is smaller and 0 if they are the same
 */
export function cmpVersions (a, b) {
	const regExStrip0 = /(\.0+)+$/;
	const segmentsA = a.replace(regExStrip0, "").split(".");
	const segmentsB = b.replace(regExStrip0, "").split(".");

View on GitHub (pinned to 4b4a59534f)

Solutions

1. Upgrade MagicMirror to at least the version the module requires (git pull / npm update in the MagicMirror directory, or update the Docker image).
2. If you must stay on the old core, checkout an older tag/branch of the module compatible with your version.
3. Check window.mmVersion in the browser console to confirm the running version before debugging further.

Example fix

// shell, before (old core + bleeding-edge module)
// after:
git fetch && git checkout release/current  # or the latest version tag
npm install
# module now meets requiresVersion

// run before installing/updating a module:
echo "Running: $(grep version package.json | head -1)"
# compare with the module's requiresVersion in its js file
grep -n requiresVersion modules/<name>/<name>.js

When it happens

Trigger: Installing a module whose requiresVersion (e.g. "2.15.0") is newer than the running MagicMirror version (e.g. 2.13.0); Module.register is called during bootstrap and returns early.

Common situations: Cloning a module's latest master branch into an outdated MagicMirror install; upgrading a module without upgrading MagicMirror core; running a distribution/fork that lags upstream.

Related errors

• Version is incorrect. Skip module: '${moduleName}'

AI-assisted analysis of MagicMirrorOrg/MagicMirror@4b4a59534f (2026-08-31). Data as JSON: /api/errors/3f4d4d2f4573210c. Report an issue: GitHub.