MMM-NowPlayingOnSpotify stop working after v2.13 update

[panos]

@sdetweil
I don’t remember exactly, but I think that it was working 3-4 days ago

[chassain 0]

i have spotify in a raspberry with a old update…I’m going to check if script is ok with this module

[chassain 0]

doing test run processing complete for all modules in first

[sdetweil]

@panos and if you use spotify client on some other device it works ok?

[panos]

@chassain-0
I don’t know why this happens then.
I run npm install on more time and rerun the authentication process via browser. (In order to update the token)
Still the same error.

[chassain 0]

@panos i’m running the script for this raspberry…wait and i give you the result

[panos]

@sdetweil
Yes. I’m able to listen via Spotify app on both mobile/desktop

[chassain 0]

always in running

[panos]

@chassain-0
Thanks
I update mine via “git pull && npm install” command

[chassain 0]

@panos
use sdetweil script…it’s better

[chassain 0]

@sdetweil

what i need to do after ?

[panos]

@chassain-0 so the module can’t work because the request-promise-native package is deprecated?

[sdetweil]

@panos no…deprecated means don’t use it new anymore, and plan to change now for any existing… will take a year or more to remove…

[panos]

@sdetweil ok I see, thanks.
So is there any workaround to make the module to work again?

[chassain 0]

@panos i’m waiting instructions to continue…If i do a restart mm i have a black screen

[sdetweil]

@chassain-0 @panos are your system clocks right?

looking thru the causes for the error…

[chassain 0]

i don’t know if git stash pop is necessary

[panos]

I haven’t had black screen once I updated to v2.13.
seems that only some modules need the “npm install” command

[sdetweil]

@chassain-0 well, you asked to save the changes… what are they and why? stash pop is the only way to get them back, but they might break other changes depending on what the changes are

[sdetweil]

@panos if they have a package,json, you should npm install (what my script does)