Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

problem with npm start

See original GitHub issue

npm.txt

Teenshali@DESKTOP-M6H39SM MINGW64 ~/MagicMirror $ npm start

magicmirror@2.11.0 start C:\Users\Teenshali\MagicMirror DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

‘DISPLAY’ is not recognized as an internal or external command, operable program or batch file. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.11.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the magicmirror@2.11.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Teenshali\AppData\Roaming\npm-cache_logs\2020-04-02T13_24_03_240Z-debug.log

Teenshali@DESKTOP-M6H39SM MINGW64 ~/MagicMirror

Issue Analytics

State:
Created 3 years ago
Comments:9 (1 by maintainers)

Top GitHub Comments

1reaction

sdetweilcommented, Apr 5, 2020

@Teenshali10 I think this is a newly discovered roboto-fontface install problem…

do this

edit vendor/package.json and change the version of roboto-fontface like this from

   "dependencies": {
    "roboto-fontface": "^0.8.0"
  }

  "dependencies": {
    "roboto-fontface": "latest"
  }

them in the vendor folder do npm install

then try to restart mm…

please advise your results

0reactions

stale[bot]commented, Jun 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.