The latest version of npm no longer accepts deprecated commands and the Travis nodeJS build is pulling this command in from somewhere that isn’t the project .travis.yml. [image] Is this running in the background somewhere? I tried searching the travis build github repo for traces of this but can’…

We are having the same issue. Was hoping that upgrading to Node 20 would get rid of the message, but it is still there. Would be really nice if someone from Travis could see this as it doesn’t seem possible to override anything in .travis.yml

Travis says this is now resolved and I no longer see it in my builds.

`npm ERR! `spin` is not a valid npm option`

Languages Node.js

fullsushidev October 10, 2023, 9:06am 2

I’ve been having the same issue and couldn’t find a fix other than downgrading my npm version to 17.
I’d like to see the travis team input tho.

Topic		Replies	Views
The command "npm config set spin false" failed and exited with 1 during Node.js	8	9759	December 16, 2022
Job fails for no good reason Node.js	2	966	February 21, 2019
Upgrade Yarn to a newer version Node.js	4	2590	May 14, 2019
Node project generating error from rvm after_use hook Travis CI Discussions & Feedback	2	535	January 11, 2019
How can I specify the package version? Environments	3	1308	August 29, 2019

`npm ERR! `spin` is not a valid npm option`

Related topics