Consolidation of multiple similar libraries
Hi @mysticatea and @k88hudson! Thanks for your hard work with `npm-run-all`! I maintain a similar library - the functionality is slightly different but it shares a lot of common functionality with `npm-run-all`. My library is called [parallelshell](https://github.com/keithamus/parallelshell) - which I maintain with @paulpflug. I am also aware of a few other libraries that attempt to solve the problem of properly parallelising npm (or shell) tasks: - [`concurrently`](https://github.com/kimmobrunfeldt/concurrently) which is written by @kimmobrunfeldt and has had contributions from @luv2code. - [`shell-executor`](https://github.com/royriojas/shell-executor) which is written by @royriojas. - [`npm-parallel`](https://github.com/spion/npm-parallel) which is written by @spion - [`pkgrun`](https://github.com/reggi/pkgrun) which is written by @reggi We're all trying to reach the same goal - run npm tasks quickly and easily in parallel (and sometimes serially), and have them log & exit in ways you'd expect. For the most part, each of us (I presume) has convergently developed these solutions. While it's great that we're all solving this problem, its bad that we're _all_ solving it... ### The point I think we should combine forces, to make one canonical parallelisation tool. Personally, I see no point in continuing development of both `parallelshell` and `npm-run-all` - we may as well just have one. Having said that, I'm still using `parallelshell` because it solves particular bugs th
Posted by keithamus on Oct 16, 2015, 2:40 PM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
Consolidation of multiple similar libraries
Hi @mysticatea and @k88hudson! Thanks for your hard work with `npm-run-all`! I maintain a similar library - the functionality is slightly different but it shares a lot of common functionality with `npm-run-all`. My library is called [parallelshell](https://github.com/keithamus/parallelshell) - which I maintain with @paulpflug. I am also aware of a few other libraries that attempt to solve the problem of properly parallelising npm (or shell) tasks: - [`concurrently`](https://github.com/kimmobrunfeldt/concurrently) which is written by @kimmobrunfeldt and has had contributions from @luv2code. - [`shell-executor`](https://github.com/royriojas/shell-executor) which is written by @royriojas. - [`npm-parallel`](https://github.com/spion/npm-parallel) which is written by @spion - [`pkgrun`](https://github.com/reggi/pkgrun) which is written by @reggi We're all trying to reach the same goal - run npm tasks quickly and easily in parallel (and sometimes serially), and have them log & exit in ways you'd expect. For the most part, each of us (I presume) has convergently developed these solutions. While it's great that we're all solving this problem, its bad that we're _all_ solving it... ### The point I think we should combine forces, to make one canonical parallelisation tool. Personally, I see no point in continuing development of both `parallelshell` and `npm-run-all` - we may as well just have one. Having said that, I'm still using `parallelshell` because it solves particular bugs th
Comments (0)
No comments yet. Start the discussion.