Nate Fischer

Where does the `./` come from? Your package.json doesn't show a `./` before the path. Was that a typo or is that being added at runtime (perhaps by `npm`)?

Travis wipes old data when you rebuild. But, it was indeed a timeout.

This will be fixed in the next shelljs release. This is a breaking change in shelljs, so it might take a bit to get it released. Keeping this open since...

@niieani Could you give an example of how to run a command under Windows? ##### Case 1: same directory ``` bash $ ./foo ``` ##### Case 2: Subdirectory ``` bash...

I think that's really about setting environmental variables. If you only want a cross-platform way to run commands, I think you can use `path/to/binary` (assuming it has one or more...

Hmmm interesting. I'll investigate when I boot up my Windows machine. We may also want to consider modifying the PATH to allow for executing binaries installed from local node module...

This is a known limitation of ShellJS's [`find()` method](https://github.com/shelljs/shelljs#findpath_array). First step would be supporting the `-type` flag over there. I think shx could translate "-name" to shelljs's expected syntax, similar...

-name is just the default argument. Try `cd BUILD/debug && shx find '**/*.o'`.

My point above was that we could probably translate that within shx itself (merge default arg + `-name` into shelljs's expected input). But there's little point for doing so right...

Last thing to fix is: ``` npm WARN prepublish-on-install As of npm@5, `prepublish` scripts are deprecated. npm WARN prepublish-on-install Use `prepare` for build steps and `prepublishOnly` for upload-only. npm WARN...