MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Depreciation Warning



  • I’ve very new to this, and I’m a little stuck. As far as I can tell I’ve followed all the instructions I could find, but I don’t know what to do from here. Any advice would be appreciated.

    (node:27999) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
    npm WARN package.json current-week-number@1.0.7 license should be a valid SPDX license expression
    npm WARN package.json rrule-alt@2.2.8 No license field.
    npm WARN package.json valid-url@1.0.9 No license field.
    npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
    npm ERR! Error: Method Not Allowed
    npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
    npm ERR!     at /usr/share/npm/lib/cache/add-named.js:203:12
    npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
    npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)
    npm ERR! If you need help, you may report this *entire* log,
    npm ERR! including the npm and node versions, at:
    npm ERR!     
    
    npm ERR! System Linux 4.14.79-v7+
    npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
    npm ERR! cwd /home/pi/MagicMirror
    npm ERR! node -v v8.11.1
    npm ERR! npm -v 1.4.21
    npm ERR! code E405
    npm ERR! 
    npm ERR! Additional logging details can be found in:
    npm ERR!     /home/pi/MagicMirror/npm-debug.log
    npm ERR! not ok code 0
    

  • Project Sponsor

    The good news is that the deprecation warning is just that: a warning. It’s more of a notice to the developers that they should move to a different package when building their systems.

    The bad news is that is definitely a bug somewhere. At first blush, it looks like one of the parameters isn’t being passed to the npm registry correctly. Is this during your initial MM install?



  • Yes. I’m going to try tor reinstall again. (Although, that didn’t work last time.) Any advice is appreciated.



  • I have the same problem.




Log in to reply