Support Existing Projects

[jimmynotjim]

Added check for an existing project

Additions

None

Removals

None

Changes

• Checks if a project already exists by searching for a local package.json
• If project exists, generator uses the manifest properties as prompt defaults
• If a project doesn't exist, defaults to the suggested prompt defaults

  Testing

• fetch and run npm link
• run yo cf on an empty directory to test original defaults but create new answers
• run yo cf again on same directory and defaults should be updated to previously created answers

  Review

• @contolini
• @ascott1
• @Scotchester

  Preview

None

Notes

• I'm also working on a PR to check for a non-standard installation location (such as what cfgov-refresh uses), but that's a bit wider scope.

[contolini]

:+1: This feature is a great idea.

[jimmynotjim]

It's not the author name it's failing at, it's the package name on L:53 (though you're definitely right about the additional author check).

[jimmynotjim]

Sweet it's fixed!

The one downside is that I'm finding is some of our projects use package.json and some bower.json. For example, OaH Bower manifest doesn't have much while the Node manifest is complete. For CFGov Refresh the Bower manifest is complete but the Node manifest is not. There's going to be some manual reconciliation for any projects that are utilizing bower.json instead of package.json.

Also, you have to be really aware when committing if you respond yes to overwriting files. Some of the overwrites you'll want (like version updates we've cleared), but if you've added Node or Bower packages to your project they'll be removed.

[contolini]

Cool, this is a great enhancement. Let's keep an eye on things to see how it works for folks.

[ascott1]

:heart: this.

[jimmynotjim]

Ran this on cfgov-refresh to get that project updated and it's currently going well. Bit of manual tweaks to match the project specifically but DiffMerge makes that easier.