Error: EISDIR

From user:

Hi!

Adviced by rauchg I'm sending a bug I just found with the recently released `up` tool.

I found that when running `up *` as it's shown on the blog post gif... and there is a `sub-directory` at the running path, then the process crashes with the following error:

Error: EISDIR, read

And no file us uploaded.

I was guessing that when a sub directory is present, `up` would zip it into a .tar or .zip file and upload it.

Or at least say that directories cannot be upload but continue uploading the rest of the files.

I'm running `node@0.10.18` with `npm@1.3.8` at a Mac OS X 10.6.8 via native terminal Darwin.

I wouldn't mind to provide with any extra information you require to debug this.

Salút!

No file or test is named. Reproduce `up *` from a directory containing a subdirectory, then trace the CLI's upload handling for directory paths. Done should be defined as either archiving the directory or reporting and skipping it while continuing other uploads, without an EISDIR crash.

Written by the indexing model from the issue text.