-
Notifications
You must be signed in to change notification settings - Fork 64
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
coffee spawns own, uncontrollable child process #50
Conversation
when using coffee as cmd the server is not restartable workaround by using node with local coffe-script instead
Changed behavior to only warn of coffee Added cmdArgs option
I changed it to only warn the user against the use of coffee |
Very similar to #47 >_< |
@paulpflug This is great work! Dumb question, but is it worth me putting in a coffee example in the |
Do you mean test? Then I would say no, because it is a bug of coffee. |
Then yes, example :) I'd like to add one to this project's |
I also committed an example to readme.md ;) |
Good enough for me. Shall I merge? |
I have to say, being able to merge this & close 5 issues sounds... good :) |
Ok. I renamed cmdArgs to opts, which is clearer.. I think |
@paulpflug et. al. (did I use that right? :D)
|
when using coffee as cmd the server is not restartable
workaround by using node with local coffe-script instead
(similar to here)
could be tested by comparing pid of child process on grunt/child side
without fix:
Starting background Express server pid of serverchild on grunt side: 3048 pid of serverchild on child side: 8812 Express server listening on port 9000 in development mode
with fix:
Starting background Express server You are using Coffee-script coffee does not allow a restart of the server found local coffee-script: ./node_modules/coffee-script/bin/coffee using nodejs with local coffe-script instead pid of serverchild on grunt side: 8416 pid of serverchild on child side: 8416 Express server listening on port 9000 in development mode