Use nouse_stdio to avoid console.log pollution from destroying json response payload #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Mr Devinus,
I have used your library with some good effect in a proof of concept project at https://github.com/robotarmy/serve_elm.
I wonder if you would consider discussing these changes and perhaps exposing configuration for enabling other options for Port.open..
I use nouse_stdio to avoid console.log statements from becoming part of the output from your wrapper script.
I think their could be some cause for exposing the working directory option for the command to Port.open and also perhaps the ENV option.
Any thoughts?!
Thank you for your great work!