MM starts but doesn't show up

Benalze

pi@raspberrypi:~/MagicMirror $ git checkout package.json
0 Paths updated from index

sdetweil

@Benalze but you did that already… I was wondering about the aliases at the bottom

Benalze

@sdetweil

},
	"optionalDependencies": {
		"electron": "^27.2.0"
	},
	"dependencies": {
		"colors": "^1.4.0",
		"command-exists": "^1.2.9",
		"console-stamp": "^3.1.2",
		"envsub": "^4.1.0",
		"eslint": "^8.56.0",
		"express": "^4.18.2",
		"express-ipfilter": "^1.3.1",
		"feedme": "^2.0.2",
		"helmet": "^7.1.0",
		"html-to-text": "^9.0.5",
		"iconv-lite": "^0.6.3",
		"module-alias": "^2.2.3",
		"moment": "^2.30.1",
		"node-ical": "^0.17.1",
		"socket.io": "^4.7.2"
	},
	"lint-staged": {
		"*": "prettier --write",
		"*.js": "eslint",
		"*.css": "stylelint"
	},
	"_moduleAliases": {
		"node_helper": "js/node_helper.js",
		"logger": "js/logger.js"
	},
	"engines": {
		"node": ">=18"
	}
}

sdetweil

@Benalze good. if the electron install went ok, then npm start

Benalze

@sdetweil
BOOM it worked.

Thank you soo sooo much. I really appreciate it!!!

Can you explain to me what was the problem?

sdetweil

@Benalze somehow you had the correct top of package.json( that’s where the number comes in the npm start messages), but an incorrect bottom of package json ( no aliases)

but git didn’t report the file being different

I can’t explain that

did u upgrade manually?

if so, in the future please use my script

Benalze

@sdetweil
Yes I upgraded manually and in the future I will use your script for sure!