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 WARN on install MM

    Scheduled Pinned Locked Moved Troubleshooting
    4 Posts 3 Posters 824 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.
    • R Offline
      renevandenbroek
      last edited by

      On a new raspberry pi with new OS I get the following WARN’s after installing MM.

      MagicMirror installation finished successfully! 
      
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      
      added 1145 packages from 643 contributors and audited 1149 packages in 155.683s
      
      84 packages are looking for funding
        run `npm fund` for details
      
      found 1 low severity vulnerability
        run `npm audit fix` to fix them, or `npm audit` for details
      

      (1.) I tried “npm audit fix” but that does not resolves the problem.

      npm WARN @octokit/plugin-request-log@1.0.2 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      
      up to date in 15.389s
      
      84 packages are looking for funding
        run `npm fund` for details
      
      fixed 0 of 1 vulnerability in 1101 scanned packages
        1 package update for 1 vulnerability involved breaking changes
        (use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)
      

      (2.) Than I did a " npm audit" with the following result

       === npm audit security report ===                        
                                                                                      
      # Run  npm install --save-dev spectron@13.0.0  to resolve 1 vulnerability
      SEMVER WARNING: Recommended action is a potentially breaking change
      ┌───────────────┬──────────────────────────────────────────────────────────────┐
      │ Low           │ Prototype Pollution                                          │
      ├───────────────┼──────────────────────────────────────────────────────────────┤
      │ Package       │ minimist                                                     │
      ├───────────────┼──────────────────────────────────────────────────────────────┤
      │ Dependency of │ spectron [dev]                                               │
      ├───────────────┼──────────────────────────────────────────────────────────────┤
      │ Path          │ spectron > webdriverio > optimist > minimist                 │
      ├───────────────┼──────────────────────────────────────────────────────────────┤
      │ More info     │ https://npmjs.com/advisories/1179                            │
      └───────────────┴──────────────────────────────────────────────────────────────┘
      
      
      found 1 low severity vulnerability in 1101 scanned packages
        1 vulnerability requires semver-major dependency updates.
      

      (3.)Than I did “npm install --save-dev spectron@13.0.0” with the following result

      > electron-chromedriver@11.0.0 install /home/pi/MagicMirror/node_modules/electron-chromedriver
      > node ./download-chromedriver.js
      
      
      > spectron@13.0.0 postinstall /home/pi/MagicMirror/node_modules/spectron
      > node lib/rpath-fix.js
      
      npm WARN @octokit/plugin-request-log@1.0.2 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      
      + spectron@13.0.0
      added 87 packages from 131 contributors, removed 107 packages, updated 16 packages, moved 2 packages and audited 1129 packages in 42.715s
      
      92 packages are looking for funding
        run `npm fund` for details
      
      found 0 vulnerabilities
      

      (4.)" npm audit" gives now

                                                                 
                             === npm audit security report ===                        
                                                                                      
      found 0 vulnerabilities
       in 1122 scanned packages
      
      

      And now what should i do with the WARN’s that came on with (3.)?

      S BKeyportB 2 Replies Last reply Reply Quote 0
      • S Offline
        sdetweil @renevandenbroek
        last edited by

        @renevandenbroek nothing. just warnings u cant do anything about

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          renevandenbroek @sdetweil
          last edited by

          @sdetweil thanks for your reply

          1 Reply Last reply Reply Quote 0
          • BKeyportB Offline
            BKeyport Module Developer @renevandenbroek
            last edited by

            @renevandenbroek developers of the underlying code are moving faster than MagicMirror can and/or is willing to update. For various calls and whatnot, the packages have changed, and even the core programs are messed up a bit, for example, some things are into double digit version numbers, which are fooling version checking that states that you have to have a version higher than a specific single digit. (It sees 1, it should be seeing 10)

            As long as it runs, you’re good.

            The "E" in "Javascript" stands for "Easy"

            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