{"action":"opened","issue":{"url":"https://api.github.com/repos/npm/npm/issues/19002","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/19002/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/19002/comments","events_url":"https://api.github.com/repos/npm/npm/issues/19002/events","html_url":"https://github.com/npm/npm/issues/19002","id":269541260,"number":19002,"title":"Error 404 when trying to install package in Windows 10 (works in Ubuntu)","user":{"login":"laurent22","id":1285584,"avatar_url":"https://avatars0.githubusercontent.com/u/1285584?v=4","gravatar_id":"","url":"https://api.github.com/users/laurent22","html_url":"https://github.com/laurent22","followers_url":"https://api.github.com/users/laurent22/followers","following_url":"https://api.github.com/users/laurent22/following{/other_user}","gists_url":"https://api.github.com/users/laurent22/gists{/gist_id}","starred_url":"https://api.github.com/users/laurent22/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laurent22/subscriptions","organizations_url":"https://api.github.com/users/laurent22/orgs","repos_url":"https://api.github.com/users/laurent22/repos","events_url":"https://api.github.com/users/laurent22/events{/privacy}","received_events_url":"https://api.github.com/users/laurent22/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-30T10:02:30Z","updated_at":"2017-10-30T10:02:30Z","closed_at":null,"author_association":"NONE","body":"#### I'm opening this issue because:\r\n\r\n  - [ ] npm is crashing.\r\n  - [ ] npm is producing an incorrect install.\r\n  - [X] npm is doing something I don't understand.\r\n  - [ ] Other (_see below for feature requests_):\r\n\r\n#### What's going wrong?\r\n\r\nI'm trying to install a package (`joplin`) on Windows 10 but it seems npm cannot fetch some data, I'm seeing this error in the log:\r\n\r\n     10 http fetch GET 404 https://registry.npmjs.org/- 448ms\r\n\r\nThe package installs fine in Ubuntu.\r\n\r\n#### How can the CLI team reproduce the problem?\r\n\r\nRun `npm -i g joplin`\r\n\r\nIt will fail and the error log will be:\r\n\r\n```\r\n0 info it worked if it ends with ok\r\n1 verbose cli [ 'C:\\\\Program Files\\\\nodejs\\\\node.exe',\r\n1 verbose cli   'C:\\\\Users\\\\Laurent\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js',\r\n1 verbose cli   'i',\r\n1 verbose cli   '-',\r\n1 verbose cli   'joplin' ]\r\n2 info using npm@5.5.1\r\n3 info using node@v8.8.1\r\n4 verbose config Skipping project config: C:\\Users\\Laurent/.npmrc. (matches userconfig)\r\n5 verbose npm-session 36726f72411c8ea2\r\n6 silly install loadCurrentTree\r\n7 silly install readLocalPackageData\r\n8 http fetch GET 304 https://registry.npmjs.org/joplin 239ms (from cache)\r\n9 silly pacote tag manifest for joplin@latest fetched in 245ms\r\n10 http fetch GET 404 https://registry.npmjs.org/- 448ms\r\n11 silly fetchPackageMetaData error for -@latest 404 Not Found: -@latest\r\n12 verbose stack Error: 404 Not Found: -@latest\r\n12 verbose stack     at fetch.then.res (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\pacote\\lib\\fetchers\\registry\\fetch.js:42:19)\r\n12 verbose stack     at tryCatcher (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\util.js:16:23)\r\n12 verbose stack     at Promise._settlePromiseFromHandler (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\promise.js:512:31)\r\n12 verbose stack     at Promise._settlePromise (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\promise.js:569:18)\r\n12 verbose stack     at Promise._settlePromise0 (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\promise.js:614:10)\r\n12 verbose stack     at Promise._settlePromises (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\promise.js:693:18)\r\n12 verbose stack     at Async._drainQueue (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\async.js:133:16)\r\n12 verbose stack     at Async._drainQueues (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\async.js:143:10)\r\n12 verbose stack     at Immediate.Async.drainQueues (C:\\Users\\Laurent\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\bluebird\\js\\release\\async.js:17:14)\r\n12 verbose stack     at runCallback (timers.js:785:20)\r\n12 verbose stack     at tryOnImmediate (timers.js:747:5)\r\n12 verbose stack     at processImmediate [as _immediateCallback] (timers.js:718:5)\r\n13 verbose cwd C:\\Users\\Laurent\r\n14 verbose Windows_NT 10.0.16299\r\n15 verbose argv \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\Users\\\\Laurent\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js\" \"i\" \"-\" \"joplin\"\r\n16 verbose node v8.8.1\r\n17 verbose npm  v5.5.1\r\n18 error code E404\r\n19 error 404 Not Found: -@latest\r\n20 verbose exit [ 1, true ]\r\n```\r\n\r\n### supporting information:\r\n\r\n - `npm -v` prints: 5.5.1 \r\n - `node -v` prints: 8.8.1\r\n - `npm config get registry` prints: https://registry.npmjs.org/\r\n - Windows, OS X/macOS, or Linux?: Windows 10\r\n - Network issues:\r\n   - Geographic location where npm was run:\r\n   - [ ] I use a proxy to connect to the npm registry.\r\n   - [ ] I use a proxy to connect to the web.\r\n   - [ ] I use a proxy when downloading Git repos.\r\n   - [ ] I access the npm registry via a VPN\r\n   - [ ] I don't use a proxy, but have limited or unreliable internet access.\r\n - Container:\r\n   - [ ] I develop using Vagrant on Windows.\r\n   - [ ] I develop using Vagrant on OS X or Linux.\r\n   - [ ] I develop / deploy using Docker.\r\n   - [ ] I deploy to a PaaS (Triton, Heroku).\r\n\r\n<!--\r\n    Thank you for contributing to npm! Please review this checklist\r\n    before submitting your issue.\r\n\r\n    - Please check if there's a solution in the troubleshooting wiki:\r\n      https://github.com/npm/npm/blob/latest/TROUBLESHOOTING.md\r\n\r\n    - Also ensure that your new issue conforms to npm's contribution guidelines:\r\n      https://github.com/npm/npm/blob/latest/CONTRIBUTING.md\r\n\r\n    - Participation in this open source project is subject to the npm Code of Conduct:\r\n      https://www.npmjs.com/policies/conduct\r\n\r\n    For feature requests, delete the above and uncomment the section following this one. But first, review the existing feature requests\r\n    and make sure there isn't one that already describes the feature\r\n    you'd like to see added:\r\n      https://github.com/npm/npm/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+label%3Aalready-looked-at\r\n-->\r\n\r\n<!--\r\n\r\n#### What's the feature?\r\n\r\n#### What problem is the feature intended to solve?\r\n\r\n#### Is the absence of this feature blocking you or your team? If so, how?\r\n\r\n#### Is this feature similar to an existing feature in another tool?\r\n\r\n#### Is this a feature you're prepared to implement, with support from the npm CLI team?\r\n\r\n-->\r\n"}}
{"actor":{"display_login":"laurent22"}}