Blaine Bublitz

@sttk I think the issue is actually that too much filesystem traversal is being made in `Liftoff.prototype.buildEnvironment` - I'm wondering if we shouldn't move https://github.com/js-cli/js-liftoff/blob/master/index.js#L62-L111 into the `execute` phase. The...

@sttk Can you help here? I'm not sure what is being requested.

@sttk I think making the change you suggest is out of scope. People have all the flexibility of node at their disposal and can even hook into the watcher instance...

Surfacing the docs from dependencies has been a big problem for us. All of it has to be done manually right now. If you'd like to send a PR, I'm...

Same for all us maintainers. Feel free to submit a PR whenever you can.

(copied from the other issue) I'm not sure which behavior I prefer because I've seen people that might want to prefix their tasks with a symbol (like a `-`). If...

In the future, maybe we can add configuration in the `.gulp.js` file to have gulp ignore flags. Here's a very rough idea: ```js module.exports = { ignoreFlags: ['--version'] }; ```...

I'm not enjoying this pushy tone. We've given some solutions and possible future enhancements. I'm sorry if that is not sufficient. As for any questions about why arguments are parsed...

@sttk I think you may have missed some more examples because the current behavior seems to match? Maybe I'm just missing it.

I noticed that a few options I wanted to expose as config options needed to be resolved before liftoff (e.g. `nodeFlags`). I'm not sure how we should resolve these problems....