Add options for flags, create list of options the project will take

[Scott-Ian]

Note: Alex mentioned using Yargs or another library for handling flags.

[AlexGaiser]

Yes @Scott-Ian I looked at

• yargs

But you should look into how if it works well with typescript

[AlexGaiser]

I am pinning this issue: @brian-ogilvie @Scott-Ian feel free to add any names for arguments you think we will need for Ian to include

[AlexGaiser]

flags / flag-names (including the ones already included in PR #18

• --typescript: if present should generate a typescript project, if absent should generate a javascript project
• --scss: if present should set project up to use scss
• --jest: if present add support for jest testing library
• --name: designate the name of the project to be defined in package.json, root directory name, etc
• --eslint: if present add support for eslint with default config
• --prettier: if present add support for prettier with default config
• --template: sets which template to use for project generation

@brian-ogilvie @Scott-Ian These are all the flags I think we will need for our mvp as defined in Issue #3. If you have any additional flags we should add add them to this comment chain. if you want ian you could add all of these to the cliOptions.ts in PR #18 or you can create a separate pull request with them included later

[brian-ogilvie]

Is --name a necessary flag? Usually name would just be the first argument passed to the command. Are you thinking that the name could be positional or optionally flagged explicitly?