Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] EMISSINGARG on npm install #588

Closed
Cohen-Carlisle opened this issue Dec 13, 2019 · 5 comments
Closed

[BUG] EMISSINGARG on npm install #588

Cohen-Carlisle opened this issue Dec 13, 2019 · 5 comments
Labels
Bug thing that needs fixing

Comments

@Cohen-Carlisle
Copy link

What / Why

error on npm install

When

  • on every npm install

Where

  • npm installed via sudo apt install npm

How

Current Behavior

  • big bad error

Steps to Reproduce

  • npm install on a default phoenix application

Expected Behavior

  • successful install

Who

  • n/a

References

  • n/a
cohen@xps-13-7390:~/code/cookbook/assets$ npm install
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated babel-preset-es2015@6.24.1: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Linux 4.15.0-1065-oem
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code EMISSINGARG

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 ERR! Please include the following file with any support request:
npm ERR!     /home/cohen/code/cookbook/assets/npm-debug.log

Contents of npm-debug.log

@ghost
Copy link

ghost commented Jan 6, 2020

I have the same issue

@everilae
Copy link

everilae commented Jan 15, 2020

We also ran into this in our Phoenix application. Upgrading webpack-cli from 2.x.x to 3.x.x in package.json under assets resolved the issue for us. We're using

  • Ubuntu 18.04 LTS
  • Node v8.10.0
  • npm v3.5.2
  • phoenix 1.4.10

@marianelamin
Copy link

I had the same issue, using Ubuntu 18.04 LTS and Node v8.10.0.

I upgraded the node version and the npm install is working just fine.

@abazzone
Copy link

abazzone commented May 12, 2020

Thanks @marianelamin. Your solution worked for me.

On my Ubuntu instance I ran these 2 commands:
# npm install -g n
# n stable

@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing
Projects
None yet
Development

No branches or pull requests

5 participants