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

Improve failed npm command log #169

Open
vmiko opened this issue Jun 16, 2023 · 0 comments
Open

Improve failed npm command log #169

vmiko opened this issue Jun 16, 2023 · 0 comments
Labels
feature request New feature or request

Comments

@vmiko
Copy link

vmiko commented Jun 16, 2023

Hi folks,

Thank you for your library. I have some suggestions to improve it.

Is your feature request related to a problem? Please describe.

I'm aware that you need to send a buildinfo to stdout and all other log messages to stderr.
But sometimes it's difficult to debug npm commands and understand what happens behind the scenes.

So, is it possible to send the stdout command result when commands go wrong ?

Try with a failed npm command that returns an error for example. Npm log messages are not very relevant on stderr. Sometimes there is useful information on stdout, but this library doesn't print it.

I have no idea, if it works the same for the other build tools (mvn, go, etc.)

Describe the solution you'd like to see

Maybe you should try to send the stdout command result in case of an error in the RunNpmCmd function before returning the error.

Describe alternatives you've considered
/

Additional context
/

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

No branches or pull requests

1 participant