Use glob and fs instead of Grunt, fixes #2

[markdalgleish]

No description provided.

[markdalgleish]

EDIT: I've fixed the broken Travis build for Node v0.8 by updating npm before installing dependencies.

[tschaub]

I've fixed the broken Travis build for Node v0.8 by updating npm before installing dependencies.

Nice. Was going to suggest the same. Unfortunate to have to do this, but until a new 0.8 is out, everybody will have to patch it.

[tschaub]

Since statSync will throw if options.base is undefined or it doesn't exist, this would have to be wrapped in try/catch to maintain previous behavior.

[tschaub]

Looks good @markdalgleish. One minor comment on error handling with a bad options.base. Would make for nicer messages for the user if we caught cases where options.base is undefined or a path to a file that doesn't exist.

[markdalgleish]

I've wrapped the fs.statSync call in a try/catch. I don't think we need to do more than that, since the error messages from fs.statSync seem pretty clear to me.

Since base is required, and defaulting to process.cwd() without any prompt to the user is a massive footgun, should we change the API to the following?

ghpages.publish(basePath, options, callback);

[tschaub]

One change this introduces is that the src config could previously be an array and could include negated patterns. But I think we can merge this and add that functionality back in separately.

ghpages.publish(basePath, options, callback);

That sounds good to me (also can be done separately).