Feature dry run

[jeffrifwald]

@ryan-roemer
Adds a dry run command that runs through the postversion and postpublish scripts using mock-fs. Addresses #5.

Here is what the dry run command looks like run on publishr itself:

[coveralls]

Coverage remained the same at 100.0% when pulling 1432277 on jmcriffey:feature-dryRun into 4119305 on FormidableLabs:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 4744307 on jmcriffey:feature-dryRun into 4119305 on FormidableLabs:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 7e3ba1e on jmcriffey:feature-dryRun into 4119305 on FormidableLabs:master.

[ryan-roemer]

If you've changed this just to be able to patch this in tests, you don't need to...

Raw:

import {exec} from "child_process";

exec();

babel output:

var _child_process = require("child_process");

(0, _child_process.exec)();

The same applies after refactoring to sinon (for sandbox.stub(childProcess, "exec")) where it would still work.

[jeffrifwald]

Good catch. I'm not sure why I thought I needed to do that.

[ryan-roemer]

@jmcriffey -- First review pass done. Let's refactor to not patch exec. Feel free to hit me up on slack if you want to chat game plan more!

[ryan-roemer]

Doesn't merely importing this start the monkey-patching of node internals? I think we want a lazy require in here right before we actually need to start doing stuff...

[jeffrifwald]

Yeah that is correct. It doesn't actually replace anything in the file system until you call it, but I'll go ahead lazy require it to make sure we correctly read the package file.

[jeffrifwald]

@ryan-roemer This is ready for another look over.

It has also been updated so that mock-fs retains the read/write permissions. This will cause the dry run to fail if you try to manipulate files without the correct permissions.

[jeffrifwald]

I like the idea of calling git status here in place of any destructive git commands to make sure git is callable.
Thoughts?

[ryan-roemer]

What are all the commands we can run? git status seems like a good dry run counterpart to git checkout. Some other git commands have a dry run capability IIRC.

[coveralls]

Coverage remained the same at 100.0% when pulling 942fd51 on jmcriffey:feature-dryRun into 4119305 on FormidableLabs:master.

[ryan-roemer]

@jmcriffey -- One question, rest lgtm without re-review unless you want it.