Comments (6)
dchambers
commented on May 13, 2024
1
I've asked a question about Linux support on the upstream issue since this fix doesn't appear to be working for me on Linux right now.
from concurrently.
jeffbski
commented on May 13, 2024
+1
from concurrently.
louy2
commented on May 13, 2024
+1
from concurrently.
kimmobrunfeldt
commented on May 13, 2024
Nothing we can do about this. NPM officially states:
That said, and taking into account everybody's feedback, I'm going to close this feature request now, because this isn't something that the team is going to have time to get to in the next 6-12 months. npm start / npm stop / npm restart are handy and convenient, but they're not substitutes for a dedicated process manager. If somebody wants to submit a patch that handles this behavior for both UNIXy systems and Windows, we'll land it, but the team isn't going to do it themselves. Thanks to everybody for their feedback!
from concurrently.
dsernst
commented on May 13, 2024
A fix for this landed in [email protected]
from concurrently.
kimmobrunfeldt
commented on May 13, 2024
Nice!! Thanks for reporting
from concurrently.
Related Issues (20)
- Filter for output of specific commands HOT 4
- Installing package from npm takes a long time HOT 4
- No colors for prefixes when using `prefixColors: "auto"` via concurrent API HOT 3
- How to combine with other node command HOT 1
- CLI options not clear in README HOT 1
- Installing package from npm cnpm yarn takes a long time HOT 2
- Logs of the commands running are not readable HOT 2
- Cancel a series of tasks with SIGINT HOT 5
- Feature Suggestion with wildcards HOT 1
- Error TS2349 using concurrently in full ESM module HOT 1
- Programmatically restarting Command using `kill/start` API produce wrong termination HOT 5
- Allow commands IPC HOT 4
- Feature request: Add or document API option to disable color output
- Prefix ([0] [1]) randomly missing HOT 1
- How to distinguish which process the output stream line comes from HOT 1
- No commands recognized when using via API HOT 1
- concurrently exitcode=0 when it receives SIGINT itself (e.g. on ^C) HOT 2
- Please change the name of the project HOT 1
- Teardown command? HOT 2
- ERR_UNHANDLED_REJECTION with `killOthers` HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from concurrently.