NodeBB v1.7.1 released!


  • Staff

    Hello folks!

    We have just released NodeBB v1.7.1.

    To see all of the closed issues included in this release, go to 1.7.1 Milestone.

    Cheers.



  • @eda said in NodeBB v1.7.1 released!:

    Hello folks!

    We have just released NodeBB v1.7.1.

    To see all of the closed issues included in this release, go to 1.7.1 Milestone.

    Cheers.

    I am seeing an error when running the upgrade command:

    $ ./nodebb upgrade
    /var/www/nodebb/forums/src/cli/index.js:39
            .description('Welcome to NodeBB')
             ^
    
    TypeError: program.name(...).description is not a function
        at Object.<anonymous> (/var/www/nodebb/forums/src/cli/index.js:39:3)
        at Module._compile (module.js:570:32)
        at Object.Module._extensions..js (module.js:579:10)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (/var/www/nodebb/forums/nodebb:5:1)
        at Module._compile (module.js:570:32)
    

  • Global Moderator

    Can you run npm ls commander to check whether it's installed?



  • @pitaj said in NodeBB v1.7.1 released!:

    Can you run npm ls commander to check whether it's installed?

    $ npm ls commander
    nodebb@1.7.0 /var/www/nodebb/forums
    ├── UNMET PEER DEPENDENCY eslint-plugin-import@1.16.0 invalid
    ├─┬ mocha@3.2.0 invalid
    │ └── commander@2.9.0  extraneous
    ├─┬ nodebb-plugin-emailer-mailgun@1.0.2
    │ └─┬ mailgun-js@0.7.11
    │   └─┬ proxy-agent@2.0.0
    │     └─┬ pac-proxy-agent@1.0.0
    │       └─┬ pac-resolver@1.2.6
    │         └─┬ regenerator@0.8.46
    │           └─┬ commoner@0.10.4
    │             └── commander@2.9.0
    └─┬ uglify-js@3.2.0
      └── commander@2.12.1
    
    npm ERR! peer dep missing: eslint-plugin-import@^2.2.0, required by eslint-config-airbnb-base@11.1.1
    npm ERR! invalid: mocha@3.2.0 /var/www/nodebb/forums/node_modules/mocha
    npm ERR! extraneous: commander@2.9.0 /var/www/nodebb/forums/node_modules/commander
    


  • eslint seemed to be the cause of various warnings and errors in npm, so I did an rm -rf ./node_modules/eslint*, ran npm install, then ran the ./nodebb upgrade again. That seems to have fixed things?


  • Admin

    Hm, that's a little weird, but I'm glad it got resolved! 😄



  • @julian said in NodeBB v1.7.1 released!:

    Hm, that's a little weird, but I'm glad it got resolved! 😄

    I assume it was a user error. I probably broke something at some point. My sledgehammer approach seems to have resolved it, and no major issues on the forum.

    Some day I will be really fancy and have a test instance...



  • @teh_g said in NodeBB v1.7.1 released!:

    rm -rf ./node_modules/eslint*

    I got eslint issues as well, but this didn't fix it for me 😞



  • Here is what we get...

    [root@lnj-lnx-mangolassi kae]# npm install
    [root@lnj-lnx-mangolassi kae]# ./nodebb upgrade
    /opt/kae-1.0/src/cli/index.js:39
    	.description('Welcome to NodeBB')
    	 ^
    
    TypeError: program.name(...).description is not a function
        at Object.<anonymous> (/opt/kae-1.0/src/cli/index.js:39:3)
        at Module._compile (module.js:570:32)
        at Object.Module._extensions..js (module.js:579:10)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (/opt/kae-1.0/nodebb:5:1)
        at Module._compile (module.js:570:32)
    

  • Admin

    @scottalanmiller check if commander is installed with npm ls commander if not try installing it with npm i commander



  • @baris said in NodeBB v1.7.1 released!:

    @scottalanmiller check if commander is installed with npm ls commander if not try installing it with npm i commander

    It was installed, but I ran the install / update command anyway and it updated it and that fixed things!



  • Ah, one addition piece, that works but you have to remove eslint first....

    rm -rf ./node_modules/eslint* ; npm i commander

  • Gamers

    Great work on fixing the issues!


  • Gamers

    Hi @scottalanmiller!

    Edit: Nvm! Figured it out. I had to update commander.


Log in to reply
 


Star

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