Skip to content

The yarn reports an error at runtime #184

Closed
Closed
The yarn reports an error at runtime#184
Labels
waiting-for-infoWaiting for more information from submitter

Description

@407chendaxia
407chendaxia
opened on Mar 10, 2019

code-server version: master branch
OS Version: windows10

When I ran the yarn at the root directory, it reports a error:

INFO Installing "logger" dependencies...
ERROR Failed to install "logger" dependencies {"error":{"killed":false,"code":1,"signal":null,"cmd":"yarn --network-concurrency 1"},"stdout":"[1/4] Resolving packages...\nsuccess Already up-to-date.\n$ if [ ! -d out ];then npm run build; fi\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.\n","stderr":"warning ..\package.json: No license field\n��ʱ��Ӧ�� !��\r\nerror Command failed with exit code 1.\n"}

Activity

  1. 407chendaxia
    added
    question
    on Mar 10, 2019

  2. sr229 commented on Mar 10, 2019

    @sr229
    sr229
    on Mar 10, 2019
    Contributor

    Hey @407chendaxia, I want to know your system info so its easier for us to diagnose the problem, typically yarn works without issues, and this seems rare.

  3. nhooyr commented on Mar 10, 2019

    @nhooyr
    nhooyr
    on Mar 10, 2019
    Contributor

    Could you provide the full log?

  4. nhooyr
    added
    waiting-for-infoWaiting for more information from submitter
    and removed
    question
    on Mar 10, 2019

  5. jeasonstudio commented on Mar 11, 2019

    @jeasonstudio
    jeasonstudio
    on Mar 11, 2019
    Contributor

    @407chendaxia 在并行安装依赖的时候会导致这个问题。也可能是GFW 的原因导致的。
    @nhooyr This problem is caused when parallel installation dependencies. It may also be that the Chinese firewall makes the installation fail.

    Maybe fix at #176

    Or add these to your .npmrc file:

    registry=https://registry.npm.taobao.org/
electron_mirror=https://npm.taobao.org/mirrors/electron
chromedriver_cdnurl=http://cdn.npm.taobao.org/dist/chromedriver
sass_binary_site=http://cdn.npm.taobao.org/dist/node-sass
disturl=https://npm.taobao.org/mirrors/node
fse_binary_host_mirror=https://npm.taobao.org/mirrors/fsevents

  6. sr229 commented on Mar 11, 2019

    @sr229
    sr229
    on Mar 11, 2019
    Contributor

    Sometime I wonder why even that firewall blocks NPM.

    China get your crap right.

  7. 407chendaxia commented on Mar 13, 2019

    @407chendaxia
    407chendaxia
    on Mar 13, 2019
    Author

    Sometime I wonder why even that firewall blocks NPM.

    China get your crap right.

    Sorry,this is not a firewall issue but a China Telecom issue. There are three telecommunications operator in China, only the China Telecom has this issue.

  8. 407chendaxia commented on Mar 13, 2019

    @407chendaxia
    407chendaxia
    on Mar 13, 2019
    Author

    Could you provide the full log?

    Could you provide the full log?

    I used this tool for the first time, I just executed the yarn command in the directory.

  9. 407chendaxia commented on Mar 13, 2019

    @407chendaxia
    407chendaxia
    on Mar 13, 2019
    Author

    Could you provide the full log?

    I followed the log and found that when I executed 'node_modules.bin>ts-node scripts\install-packages.ts', I get this error.

  10. sr229 commented on Mar 13, 2019

    @sr229
    sr229
    on Mar 13, 2019
    Contributor

    @nhooyr this is network related issue so I don't think it merits a full verbose log during yarn install

  11. nhooyr commented on Mar 13, 2019

    @nhooyr
    nhooyr
    on Mar 13, 2019
    Contributor

    The provided error doesn't indicate anything. How do you know its a network issue?

  12. sean256 commented on Mar 23, 2019

    @sean256
    sean256
    on Mar 23, 2019

    I too am having this

    ERROR Failed to install "logger" dependencies {"error":{"killed":false,"code":1,"signal":null,"cmd":"yarn --network-concurrency 1"},"stdout":"[1/4] Resolving packages...\nsuccess Already up-to-date.\n$ if [ ! -d out ];then npm run build; fi\n\n> @coder/logger@1.0.3 build /Volumes/gits/code-server/packages/logger\n> tsc -p tsconfig.build.json && cp ./out/packages/logger/src/* ./out && rm -rf out/packages && ../../node_modules/.bin/webpack --config ./webpack.config.js\n\nerror TS5023: Unknown compiler option 'emitDeclarationOnly'.\nerror TS5023: Unknown compiler option 'resolveJsonModule'.\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.\n","stderr":"warning ../package.json: No license field\nnpm ERR! code ELIFECYCLE\nnpm ERR! errno 1\nnpm ERR! @coder/logger@1.0.3 build: `tsc -p tsconfig.build.json && cp ./out/packages/logger/src/* ./out && rm -rf out/packages && ../../node_modules/.bin/webpack --config ./webpack.config.js`\nnpm ERR! Exit status 1\nnpm ERR! \nnpm ERR! Failed at the @coder/logger@1.0.3 build script.\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR!     /Users/sean/.npm/_logs/2019-03-23T03_12_28_733Z-debug.log\nerror Command failed with exit code 1.\n"}

  13. sean256 commented on Mar 23, 2019

    @sean256
    sean256
    on Mar 23, 2019

    Got it! I had a very old version of tsc installed. Being brand new to this project I didn't event know I had to have it as a global dependency.

    Maybe it would be a good idea to add something to the readme for a developing quick-start guide?

  14. sr229 commented on Mar 23, 2019

    @sr229
    sr229
    on Mar 23, 2019
    Contributor

    We'll see if the developers can provide it, because I'm afraid the developers know more how it works

  15. dijiang commented on Apr 19, 2019

    @dijiang
    dijiang
    on Apr 19, 2019

    image

    i have the same proble on win10, how to fix? @sean256

  16. dijiang commented on Apr 19, 2019

    @dijiang
    dijiang
    on Apr 19, 2019

    image

  17. dijiang commented on Apr 19, 2019

    @dijiang
    dijiang
    on Apr 19, 2019

    image
    ts-node problem?

  18. nol166 commented on Apr 19, 2019

    @nol166
    nol166
    on Apr 19, 2019
    Contributor

    Windows builds are not fully working yet

  19. kylecarbs commented on Apr 24, 2019

    @kylecarbs
    kylecarbs
    on Apr 24, 2019
    Member

    Seems like this yarn error has been fixed since we no longer install dependencies in parallel.

  20. kylecarbs
    closed this as completedon Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    waiting-for-infoWaiting for more information from submitter

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions