v14.5.0 regression with npm

[SheetJSDev]

• Version: v14.5.0
• Platform: OSX and Linux 4.15.0-1028-gcp
• Subsystem:

What steps will reproduce the bug?

$ npm install -g npm@4.3.0
$ npm install -g mocha@2.x voc

How often does it reproduce? Is there a required condition?

Every single time

What is the expected behavior?

Installs correctly (and you can verify this using node v14.4.0)

What do you see instead?

npm ERR! node v14.5.0
npm ERR! npm  v4.3.0
npm ERR! cb.apply is not a function

Additional information

Since this works in 14.4.0 and in 12.x, I'm inclined to believe this is a nodejs regression.

[addaleax]

This is happening because npm@4.3.0 uses an outdated, unsupported version of graceful-fs, which doesn’t have isaacs/node-graceful-fs@168bdb8. This is a problem because #33945 adds usage of the bigint option.

You should be able to address this by updating npm, ideally to a supported version.

[SheetJSDev]

Thanks for the explanation! And yes, updating to npm >= 6.10.0 resolves the issue

[poojaynaik]

Hello SheetJSDev,

Can you please tell me how did you upgrade the npm?
my Node version is v14.6.0 and NPM is 4.6.1
I manually degrade the npm version for some reason and now I wanted to upgrade it to the latest.
I tried doing it manually using commands like npm install -g npm@latest and npm install -g npm@5.6.0 but getting error as npm ERR! cb.apply is not a function
Can you please assist me? thank you in advance.

[SheetJSDev]

We didn't really "fix" the problem, all we did was just skip downgrading. SheetJS/sheetjs@93ec51e shows what we did for travis -- the script only messes with npm if the node version is in the v0.8.x range

To bail out of a broken npm situation, you can use something like nvm or n to switch node+npm versions (go down to 12, back up to 14) or just uninstall and reinstall from the official nodejs.org releases.

[poojaynaik]

Hey, Thank you for your feedback. It helped a lot. Thanks And Regards, Pooja Naik

…

On Thu, Jul 23, 2020 at 4:26 PM SheetJSDev ***@***.***> wrote: We didn't really "fix" the problem, all we did was just skip downgrading. ***@***.*** <SheetJS/sheetjs@93ec51e> shows what we did for travis -- the script only messes with npm if the node version is in the v0.8.x range To bail out of a broken npm situation, you can use something like nvm or n to switch node+npm versions (go down to 12, back up to 14) or just uninstall and reinstall from the official nodejs.org releases. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#34162 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANV733ECC6QCLB5YZDDJIKLR5CMIVANCNFSM4ONX4H3Q> .

[DenisCor]

node v14.16.0 and npm 7.6.0 AND I STILL GET THIS STUPID ERROR!! reinstalled node, cleaned cache.. tried everything and no luck!

[DenisCor]

Thanks for the explanation! And yes, updating to npm >= 6.10.0 resolves the issue

my npm is 7.6.0 and i still get this error

[ArchishmanSengupta]

We didn't really "fix" the problem, all we did was just skip downgrading. SheetJS/sheetjs@93ec51e shows what we did for travis -- the script only messes with npm if the node version is in the v0.8.x range

To bail out of a broken npm situation, you can use something like nvm or n to switch node+npm versions (go down to 12, back up to 14) or just uninstall and reinstall from the official nodejs.org releases.

Can you elaborate on this? what is the command to solve the issue?