Che: event-stream-3.3.6.tgz not found in Yarnpkg.

Created on 30 Nov 2018  路  12Comments  路  Source: eclipse/che

Description

See Diagnostics: below for more details.
Possibly related on the recent security incident

Reproduction Steps

Build master branch.

OS and version:

Independent

Diagnostics:

[INFO] --- maven-antrun-plugin:1.8:run (build-dashboard) @ che-dashboard-war ---
[INFO] Executing tasks

main:
     [exec] yarn install v1.12.3
     [exec] [1/5] Validating package.json...
     [exec] [2/5] Resolving packages...
     [exec] [3/5] Fetching packages...
     [exec] error https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "Unexpected end of data"
     [exec] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
curl https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz
{"error":"Not found"}
kinbug severitP1

Most helpful comment

this is due to : https://blog.npmjs.org/post/180565383195/details-about-the-event-stream-incident

to solve the issue, add the following to your package.json file :

  ...
  ,
  "resolutions": {
    "**/event-stream": "^4.0.1"
  }

All 12 comments

I'm having the same issue as well

Got it as well

this is due to : https://blog.npmjs.org/post/180565383195/details-about-the-event-stream-incident

to solve the issue, add the following to your package.json file :

  ...
  ,
  "resolutions": {
    "**/event-stream": "^4.0.1"
  }

should be fixed in master now with PR of @monaka https://github.com/eclipse/che/pull/12078

Solved after deleting yarn.lock

it worked for me to delete yarn.lock in yarn global dir

if you want to keep the yarn.lock file, just change the name yarn.lockBKP and run yarn install again!

it worked for me to delete yarn.lock in yarn global dir

and what to do, if I try to deploy it on Travis?

I think that just deleting yarn.lock will bring potential weakness. You should think how event-stream was contaminated.

deleting yarn.lock file add run yarn to generate new yarn.lock file solved the problem for me

Solved after deleting yarn.lock

this is the way to go. Thanks!

This worked for me. Thanks!
(Google brought me here for the same problem, but on a different project)

Was this page helpful?
0 / 5 - 0 ratings