-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Powershell issues #34
Comments
@AdrianoCahete Interesting. What terminal are you using? Also, what Node version? |
It's PowerShell running inside cmder.
|
Interesting. I'm running the exact same build of Powershell as you so it must be the terminal emulator that is breaking it for me. I'm using Windows Terminal but I also tried the default terminal. I'm running Node v12.13.0. It looks like this is really two separate issues. I'll be digging into it when I have time (hopefully sometime before the end of the week). |
PowershelI is a special cookie! I just added “>” and it works.
|
@jonizen That seems to just write the JSON to a file named |
Same here 😢 Edit: The regular pipe command worked fine in the command prompt. |
PowerShell won't support piping output from one non-PowerShell command to another. You can still execute the cmd version of the command via PowerShell by passing it as a parameter to cmd.
|
npm-audit-html
doesn't seem to work in Powershell. Pipingnpm audit --json
intonpm-audit-html
does not actually work. For some reason, there is nostdin
. The process just silently exits.Also, reading directly from a JSON files doesn't work in Powershell (e.g.
npm audit --json > audit.json; npm-audit-html -i audit.json
). ThereadJson
function fails due to charector encoding issues.The text was updated successfully, but these errors were encountered: