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.

Sign up for GitHub

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

Jump to bottom

NPM Errors should not _just_ have process exited with status code 1 #131

Open
bryanmacfarlane opened this issue Mar 31, 2020 · 2 comments
Open

NPM Errors should not _just_ have process exited with status code 1 #131

bryanmacfarlane opened this issue Mar 31, 2020 · 2 comments
Assignees
@bryanmacfarlane
Labels
enhancement New feature or request

Comments

@bryanmacfarlane
Copy link
Member

Errors from npm should ideally be highlighted and / or become a problem matcher
npm-err
@bryanmacfarlane bryanmacfarlane added the enhancement New feature or request label Mar 31, 2020
@bryanmacfarlane bryanmacfarlane changed the title NPM Errors should not just have process exited with status code 1 NPM Errors should not _just_ have process exited with status code 1 Mar 31, 2020
@bryanmacfarlane bryanmacfarlane self-assigned this Mar 31, 2020
@thomas-schuster
Copy link

Is there a possibility to access the error log if an actions workflow is executed on GitHub environment?

@Jamawre
This comment has been minimized.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bryanmacfarlane bryanmacfarlane

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bryanmacfarlane @thomas-schuster @Jamawre