Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yarn 4 fails with --color=always #591

Open
cgen01 opened this issue Oct 24, 2023 · 0 comments
Open

Yarn 4 fails with --color=always #591

cgen01 opened this issue Oct 24, 2023 · 0 comments

Comments

@cgen01
Copy link

cgen01 commented Oct 24, 2023

When running normally npm-check -u, after selecting the packages, the install fails:

$ yarn add [...] --color=always
Command failed with exit code 1: yarn add [...] --color=always
Unknown Syntax Error: Command not found; did you mean one of:

  0. yarn add [--json] [-F,--fixed] [-E,--exact] [-T,--tilde] [-C,--caret] [-D,--dev] [-P,--peer] [-O,--optional] [--prefer-dev] [-i,--interactive] [--cached] [--mode #0] ...
  1. yarn add [--json] [-F,--fixed] [-E,--exact] [-T,--tilde] [-C,--caret] [-D,--dev] [-P,--peer] [-O,--optional] [--prefer-dev] [-i,--interactive] [--cached] [--mode #0] ...

While running add [...] --color=always
TypeError: Cannot read properties of null (reading 'renderSync')
    at /Users/cgen01/.nvm/versions/node/v18.17.1/lib/node_modules/npm-check/lib/cli.js:151:52
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

If I run it like this npm-check -u --no-color, it works but looks bland. Is there a way to update this to support Yarn 4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant