Open Raynos opened 10 years ago
Should we call it ngen-version
or uber-ngen-version
? We are kind of co-opting an already-existing library's namespace with the former.
The rest looks fine to me, except it should also automatically create a branch to apply the patch onto, so it's easy for the user to turn it into a PR/arc diff thing?
good idea.
This is the biggest thing I'm looking for when looking at generators and scaffolding: with a ton of modules, we don't want to be stuck with manually updating them to new scaffolding versions.
@Raynos: has the version field been added, even if the diff part has not?
@terinjokes yes the version field is in
whenever we change uber-ngen it's hard to update everything that was generated.
Here's a concept of how to do this
ngen-version
field in the package.json that's scaffolded that marks the version of ngen used to generate this projectuber-ngen update
command that updates an existing project to the latest version of the ngen scaffolderTo start we should add the ngen-version to the package.json