MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    npm start doesn't do anything but logs random words.

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    9 Posts 3 Posters 1.7k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Do not disturb
      sdetweil @Ichiritzu
      last edited by

      @ichiritzu reflash, then use my script. don’t do anything else before that

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      I 1 Reply Last reply Reply Quote 0
      • I Offline
        Ichiritzu @sdetweil
        last edited by

        @sdetweil Ok, I reflashed and got Bullseye. Then I immediately followed your script and the same results. After installing nothing happens, it just instructs me to cd to MagicMirror and use pm2 start MagicMirror.

        When I do that, still nothing happens. It says status online, cpu 0%, and memory 2.8mb. Also when I do npm start, all it does is log random words like before.

        S 1 Reply Last reply Reply Quote 0
        • S Do not disturb
          sdetweil @Ichiritzu
          last edited by

          @ichiritzu someone on discord is reporting similar issues…

          he said renaming mm folder and doing manual install

          git clone && npm install worked.

          not sure what is going on

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          karsten13K 2 Replies Last reply Reply Quote 0
          • karsten13K Online
            karsten13 @sdetweil
            last edited by

            see https://www.bleepingcomputer.com/news/security/dev-corrupts-npm-libs-colors-and-faker-breaking-thousands-of-apps/

            1 Reply Last reply Reply Quote 1
            • karsten13K Online
              karsten13 @sdetweil
              last edited by

              @sdetweil

              it seems to be solved now, npm delivers now colors v1.4.0 as max version …

              I 1 Reply Last reply Reply Quote 0
              • I Offline
                Ichiritzu @karsten13
                last edited by

                @karsten13 @sdetweil

                Awesome! thank y’all. I finally fixed by renaming the folder, changing the dependency ‘colors’ to 1.4.0 (removed the carrot), delete node_modles, and npm install.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post
                Enjoying MagicMirror? Please consider a donation!
                MagicMirror created by Michael Teeuw.
                Forum managed by Sam, technical setup by Karsten.
                This forum is using NodeBB as its core | Contributors
                Contact | Privacy Policy