error An unexpected error occurred: “https://registry.yarnpkg.com/faker/-/faker-3.1.0.tgz: unexpected end of file”

you want to report a bug?

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

I am getting this error whenever I am using the docker-compose up command and then it goes to resolving issues and then gives out some warning and this error. please help
screenshot from 2019-01-27 11-34-51

Please mention your node.js, yarn and operating system version.
ubuntu 18.04
yarn 1.13.0
node v8.15.0

Author: Fantashit

3 thoughts on “error An unexpected error occurred: “https://registry.yarnpkg.com/faker/-/faker-3.1.0.tgz: unexpected end of file”

  1. It’s also happening for us in Google Cloud Functions builds, for instance:

    ⚠  functions[<redacted>(us-central1)]: Deployment error.
    Build failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "`yarn_install` had stderr output:\nwarning Resolution field \"hoist-non-react-statics@3.1.0\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"hoist-non-react-statics@3.1.0\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"hoist-non-react-statics@3.1.0\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"hoist-non-react-statics@3.1.0\" is incompatible with requested version \"hoist-non-react-statics@^3.3.0\"\nwarning Resolution field \"hoist-non-react-statics@3.1.0\" is incompatible with requested version \"hoist-non-react-statics@^2.5.0\"\nerror An unexpected error occurred: \"https://registry.yarnpkg.com/grpc/-/grpc-1.22.2.tgz: unexpected end of file\".\n\nerror: `yarn_install` returned code: 1", "errorType": "InternalError", "errorId": "00D4E024"}}
    

    For clarity, here is the end of the errorMessage:

    error An unexpected error occurred: "https://registry.yarnpkg.com/grpc/-/grpc-1.22.2.tgz: unexpected end of file".
    error: `yarn_install` returned code: 1
    

    This is becoming a main blocker during our deployment process 😕

Comments are closed.