Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

nested run-script output is overpowering on error #9421

Closed
othiym23 opened this issue Aug 26, 2015 · 1 comment
Closed

nested run-script output is overpowering on error #9421

othiym23 opened this issue Aug 26, 2015 · 1 comment

Comments

@othiym23
Copy link
Contributor

For a particularly ridiculous example, see the following:
2015-08-26_15-59-20_lz8ww
2015-08-26_15-58-43_1qs29

There should probably be at most a single set of output when a run-script run fails, regardless of how many times npm run is calling itself.

It would also be nice if npm run were smart enough to notice when it's calling itself and not create another Node process until it's running something that's not npm.

@npm-robot
Copy link

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants