NodeBB v1.7.1 released!

[teh_g]

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?

[julian]

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

[teh_g]

@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...

[scottalanmiller]

@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

[scottalanmiller]

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)

[baris]

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

[scottalanmiller]

@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!

[scottalanmiller]

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

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

[faizanzahid]

Great work on fixing the issues!

[Michael Pfaff]

Hi @scottalanmiller!

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