npm depreciation warnings with current install



  • I am spinning up a new community and found the following warnings during my install.

    Anything I should do about these?

    [root@bna-com ~]# nvm install v7.2.0
    ######################################################################## 100.0%
    Computing checksum with sha256sum
    Checksums matched!
    Now using node v7.2.0 (npm v3.10.9)
    Creating default alias: default -> v7.2.0
    [root@bna-com ~]# cd /opt/bnacmty/
    [root@bna-com bnacmty]# git clone -b v1.x.x https://github.com/NodeBB/NodeBB nodebb
    Cloning into 'nodebb'...
    remote: Counting objects: 112796, done.
    remote: Compressing objects: 100% (101/101), done.
    remote: Total 112796 (delta 38), reused 2 (delta 2), pack-reused 112693
    Receiving objects: 100% (112796/112796), 34.86 MiB | 9.87 MiB/s, done.
    Resolving deltas: 100% (84665/84665), done.
    [root@bna-com bnacmty]# cd nodebb
    [root@bna-com nodebb]# npm install
    npm WARN deprecated node-uuid@1.4.7: use uuid module instead
    npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
    npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
    npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
    npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
    nodebb@1.3.0 /opt/bnacmty/nodebb
    

Log in to reply
 

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.