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 install --verbose #763

Closed
indieisaconcept opened this issue Oct 11, 2016 · 5 comments
Closed

yarn install --verbose #763

indieisaconcept opened this issue Oct 11, 2016 · 5 comments
Assignees

Comments

@indieisaconcept
Copy link

indieisaconcept commented Oct 11, 2016

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

Feature : This would make diagnosing installation issues much easier. See #764 for more context.

What is the current behavior?

Running yarn --verbose or yarn install --verbose does not display extended information about the installation process.

What is the expected behavior?

Should provide extended output similar to npm i --verbose

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

  • yarn@v0.15.1
  • node@v4.4.6
  • osx@10.10.5
@bestander
Copy link
Member

To debug issues we have on CI servers I'd like to have a log of all files being copied during linking phase.

@Daniel15
Copy link
Member

There's some discussion in #1500 too (which I closed in favour of this one)

@sebmck sebmck self-assigned this Nov 22, 2016
sebmck pushed a commit that referenced this issue Nov 22, 2016
@sebmck
Copy link
Contributor

sebmck commented Nov 22, 2016

Created #1994 to fix this, pending approval.

@indieisaconcept
Copy link
Author

Thanks!.

sebmck pushed a commit that referenced this issue Nov 24, 2016
* Add verbose flag - fixes #763

* fix lint

* fix lint add verboseInspect method
bestander pushed a commit to bestander/yarn that referenced this issue Nov 24, 2016
* Add verbose flag - fixes yarnpkg#763

* fix lint

* fix lint add verboseInspect method
@sam0x17
Copy link

sam0x17 commented Aug 27, 2021

In some cases this is still insufficient -- without an environment variable to force verbose mode, there is no way to force verbose mode when debugging yarn output when yarn is being called by a web framework that simply shells out to yarn install (what I'm currently dealing with). If there was like YARN_VERBOSE=true I could avoid my current situation.

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

6 participants