You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
For a particularly ridiculous example, see the following:
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.
The text was updated successfully, but these errors were encountered:
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.
For a particularly ridiculous example, see the following:
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.The text was updated successfully, but these errors were encountered: