[BUG] Missing required argument #1

[HotGreenPeas]

npm ERR! typeerror Error: Missing required argument #1
npm ERR! typeerror at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
npm ERR! typeerror at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
npm ERR! typeerror at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12)
npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
npm ERR! typeerror at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
npm ERR! typeerror at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
npm ERR! typeerror at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror This is an error with npm itself. Please report this error at:
npm ERR! typeerror http://github.com/npm/npm/issues

npm-debug.log

[byv55f5f5]

Same here

[cerpusoddarne]

Same problem here.

[revoltek-daniel]

Same Problem here.
Deployment stops working today, on friday the build was completed without problems.

[Mico27]

Same problem, Nothing changed since friday and it was working fine then.

[RyanMannix]

Same problem.

It appears something was released that breaks older versions of npm (we were using 3.5.2, the most current version using apt-get). We fixed this by updating to the latest version of npm as a RUN command in our Dockerfile

RUN npm install -g npm@latest

We were installing npm via apt-get in a list of apt installs, but the latest release of npm isn't available through the apt install option. So, after we install the old version of npm in the apt list we updated it on the next line of the Dockerfile with the command above. Hopefully updating it will not break anything you're doing, and hope this helps some of you.

[pettazz]

Ran into this as well, installing npm@latest seems to be a good enough workaround for now.

[mikemimik]

@RyanMannix is there a chance you could provide some information about that Dockerfile?
Q: Which version of apt are you using?
Q: Does the Dockerfile run apt update before it installs packages?
Q: What repository/ies is/does apt point to?

---

The original issue has a npm-debug.log file that references npm@3.5.2 and node@8.10.0. As of January 1st, 2020 node@8 is no longer LTS maintenance is isn't supported by the OpenJS Foundation. If it's at all possible to update to node@10, it comes with npm@6.13.4 which is a much newer version than npm@3.5.2 (many changes and improvements).

If you're stuck at node@8, then I would recommend to anyone following that simply adding

RUN npm install -g npm@latest

to your Dockerfiles in order to get builds/deploys working again. I've created a TODO for myself to ask our engineering team if there were changes put forth on Friday.

---

Thanks for everyone speaking up about this and @pettazz for tweeting about it :D

[ljharb]

@mikemimik its notable tho that this seems caused by a registry-side change, since it’s only started happening recently. I’ve seen it on node 5 on windows on npm versions that previously worked.