Closed sttk closed 6 years ago
@sttk thanks for submitting this. I'm keeping this in the back of my mind to see if we can solve it in a cleaner way.
@sttk I'm just outlining some thoughts but what if this library took a argv
option. If it is a function, it can received the buildEnvironment and return the argv
it wants to use instead of process.argv
. It seems more flexible that modifying the in-process process.argv
object. Thoughts?
@phated I've rebased and tried to add opts.argv which can be specified an array or a function. Is this along with your thought?
@sttk are you planning to update this soon to use the flagged-respawn updates?
@phated Yes, and I've recreated and pushed now!
I don't know the cause of the failure, but it succeeded on my test env.
@sttk I'm not happy with the option name nodeFlags
- I'll probably rename it in the merge.
Merged as b3df2f5e1673ac3994dc07a4c1421148aac62737
@sttk Thank you so much for taking the time to solve this elegantly. I'm very happy with this implementation!
@phated I see and I think your naming is better. Thanks for merging.
Published as 2.5
This pr is for giving a liftoff application a change to configure node flags.