-
-
Notifications
You must be signed in to change notification settings - Fork 241
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.
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
Feature request: wait for message on stdout before continuing #43
Comments
Thank you for this issue. Hmm, sorry, I don't want to add the feature to wait for specified message. There are some workarounds.
|
I understand, it could get a little messy. Thank you for the quick answer and help though, and |
@mysticatea
In the case of above, webpack's first build runs twice. (And the first build is slower than the continuous build.)
However it is not waiting if Should I do like this?
Otherwise wait for the stdout as described in this issue? |
@robario if it helps, I ended up doing this: "scripts": {
"prebuild": "rimraf _built",
"build": "tsc",
"watch": "npm-run-all prebuild -p watch:*",
"watch:tsc": "tsc -w",
"watch:nodemon": "wait-on _built/server.js && nodemon _built/server.js --watch _built"
}
|
@poislagarde |
Closing as I don't want to add this feature. |
Hey! I'm setting up a node server with TypeScript, and I'd like to spawn
tsc -w
(compile + watch .ts files) in parallel withnodemon
(watch compiled .js files + restart server).The problem is that I need to delay the spawning of
nodemon
untiltsc
is done compiling.I think it would be very useful if we could tell
npm-run-all
to wait for a message to appear on stdout before continuing to spawn tasks.What do you think? If you guys think it's a good idea I can try to put together a PR. Of course I could use some pointers in that case.
The text was updated successfully, but these errors were encountered: