Closed ryan-roemer closed 8 years ago
I've reproduced and am checking out node 4+ CI failures.
UPDATE: Node 4+ can't require
from a mocked filesystem. Updated with a test stub, fixed, and rebased.
Coveralls Note: CI decrease is acceptable as it's user prompts for destination
that we normally mock out anyways. I'll leave the red lines for now and we can add coverage / tickets if needed later.
Aside from some confusion on the docs, this looks good. I'd like another reviewer to look over the process
and fs
code chunks in case I missed a potential problem deep in node.
This is a metric ton of good work! Tested out the binary, worked like a charm. :+1: :100: :shipit:
@rgerstenberger @coopy -- Thanks for the review! Rebasing and going for the merge!
Everyone else -- post-merge review welcome!
Released as builder-init@0.0.1
!
At long last,
builder-init
is (hopefully) ready for prime time!Overview
We use a process spawn of
npm pack
to do the heavy lifting for downloading archetype tarballs from file, npm, git, etc. We then expand the tarballs in a temp directory and process them into an outputted project.builder-init --help
. Fixes #5builder-init --version
.builder-init <archetype> --prompts=JSON
helper for automation.Kicking the Tires
This should work:
from the parallel PR https://github.com/FormidableLabs/builder-react-component/pull/33
Usage
Sample Flow
Review
Admittedly, this PR is a biggie, so appreciate any review we can get here. However, the bulk of the line changes are in the tests, and we've now got pretty comprehensive coverage of some awkward corner cases that can arise.
/cc @coopy @benbayard @chaseadamsio @exogen @boygirl @zachhale @kenwheeler @jstrimpel @baer