Closed sandyklark closed 6 years ago
I'd recommend splitting the generator into subgenerators instead. An existing repo would likely already have Git initialised, so any changes should be visible to the committer.
:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Description
A prompt at the start of the generator that allows a project to be updated instead of generated.
What is the use case that should be solved?
This should do things like:
package.json
If there is additional config how would it look?
An additional prompt at the start of the generator prompts that lets the user know an existing
package.json
has been detected, the user can then choose toappend
,abort
oroverwrite
.Similar or dependent issues:
Additional Data
Version of
generator-nodejs-ts
you're using: 1.1.0Node Version: 8.11.4
Operating System: osx 10.13