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
Licence generateDisclaimer - Outputs "junk" to stdout #1191
Labels
Comments
I'd like to start contributing so I'm going to work on this. |
tlent
added a commit
to tlent/yarn
that referenced
this issue
Oct 27, 2016
Previously 'yarn licenses generate-disclaimer' would not include the output wrapper header and footer but other valid variations such as 'yarn licenses generateDisclaimer' would. Fixes yarnpkg#1191
Created #1586 to fix this, pending approval. |
Hi All, I seem to still have this problem:
Is there any way to fix this? Thanks! NINJA EDIT: I can run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When running
yarn licenses generateDisclaimer
and piping stdout to a file, I would expect to get only the disclaimer text to easily integrate this feature with CI etc. Instead, the first few lines look like this:The third line is correct, but the two proceeding have nothing to do with the disclaimer.
At the end of the document, there is a line that says
This is also not a part of the disclaimer and should not be a part of the output.
I see four possible solutions.
yarn
tostderr
generateDisclaimer
-q, --quiet
flag-o --output
option togenerateDisclaimer
that writes a fileIf the current behavior is a bug, please provide the steps to reproduce.
yarn licenses generateDisclaimer > DISCLAIMERS.txt
DISCLAIMERS.txt
What is the expected behavior?
The disclaimer file is generated without the parts preceding
THE FOLLOWING SETS FORTH ATTRIBUTION
, and withoutDone in 5.45s.
at the end.Please mention your node.js, yarn and operating system version.
The text was updated successfully, but these errors were encountered: