After playing with the results on #386 locally for a bit I've realised what would be most useful is if a scoped bootstrap command bootstrapped all the dependencies of packages first.

• If used without --scope it would ignore this.
• Would need some logic to sort out the order of installation if more than one package is matched by --scope

The use case for us is lots of packages now taking a long to time prepublish and link. --scope helps a lot but not in the case where you've done a clean and just want to start working on one package. You would try to scope to the package you want but your dependencies wont be built.

I can see #384 being super useful for this. If we have a direction on #384 and #386 then I can start working on this next week if you like.

(--with-deps is a terrible name, any suggestion would be appreciated. --recursive maybe? --bootstrap-deps?)