Yarn: Yarn fails to install certain packages (Error Request failed "404 Not Found")

[TyOverby]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Yarn fails to install @types/webpack at version 4.1.1

package.json

    "@types/webpack": "^4.1.1",

  Error: https://registry.yarnpkg.com/@types/webpack/-/webpack-4.1.1.tgz: Request failed "404 Not Found"
      at new ResponseError (/usr/lib/node_modules/yarn/lib/cli.js:238:112)
      at Request.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:61626:26)
      at emitOne (events.js:116:13)
      at Request.emit (events.js:211:7)
      at Request.module.exports.Request.onRequestResponse (/usr/lib/node_modules/yarn/lib/cli.js:133316:10)
      at emitOne (events.js:116:13)
      at ClientRequest.emit (events.js:211:7)
      at HTTPParser.parserOnIncomingClient (_http_client.js:551:21)
      at HTTPParser.parserOnHeadersComplete (_http_common.js:115:23)
      at TLSSocket.socketOnData (_http_client.js:440:20)

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

It installs

Please mention your node.js, yarn and operating system version.

yarn version: 1.5.1
operating system: Ubuntu 16.3
nodejs version: v8.10.0

[TyOverby]

Interestingly, https://registry.yarnpkg.com/@types/webpack/-/webpack-4.1.1.tgz is an invalid url, but https://registry.yarnpkg.com/@types/webpack/webpack-4.1.1.tgz is fine. No idea how that extra dash got there.

[lobboblaw]

Seeing something similar:

Error: https://registry.yarnpkg.com/@types/webpack/-/webpack-3.8.9.tgz: Request failed "404 Not Found"
      at ResponseError (/usr/share/yarn/lib/cli.js:163:5)
      at Request.<anonymous> (/usr/share/yarn/lib/cli.js:59356:26)
      at emitOne (events.js:96:13)
      at Request.emit (events.js:188:7)
      at Request.module.exports.Request.onRequestResponse (/usr/share/yarn/lib/cli.js:123971:10)
      at emitOne (events.js:96:13)
      at ClientRequest.emit (events.js:188:7)
      at HTTPParser.parserOnIncomingClient (_http_client.js:474:21)
      at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      at TLSSocket.socketOnData (_http_client.js:363:20)

It was working earlier this afternoon.

[TyOverby]

@lobboblaw: Yep, can confirm that it broke in the last 3 hours.

[kraenhansen]

I am seeing this with npm as well.

[kraenhansen]

See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/24347

[geomorillo]

im seeing this on npn with aureliajs

[Alexander-Taran]

Interestingly, https://registry.yarnpkg.com/@types/webpack/-/webpack-4.1.1.tgz is an invalid url, but https://registry.yarnpkg.com/@types/webpack/webpack-4.1.1.tgz is fine. No idea how that extra dash got there.

npm -i does the same..

[Alexander-Taran]

registry issue resolved:
https://github.com/npm/registry/issues/292

so this one probably can be closed

[Cherviakov]

Error 404 on that link @Alexander-Taran

[chrislam]

registry issue resolved:
https://github.com/npm/registry/issues/292

so this one probably can be closed

Updated link to the npm registry issues archive
https://github.com/npm/registry-issue-archive/issues/292