init command

[prisma-labs]

init command

[jasonkuhrt]

oclif uses yeoman internally for its init workflows. Maybe we want to explore why they chose this direction, understand the tradeoffs, etc.

[jasonkuhrt]

It would be nice if, when user scaffolds a project they seamlessly transition into dev mode. This has a few implications:

• global pumpkins package needs to transition to using local pumpkins package seamlessly

• we want to support scaffolding a new project and working with pumpkins as a kind of lightweight cli tool (e.g. just having a schema.ts module is enough to prototype).

  • These are contradictory because one mode/view thinks its ok to work with an empty folder while the other mode/view thinks it implies "lets start a new project".

  • We could solve this by a default behaviour with alt behind a flag. For example pumpkins start vs pumpkins start --create. Or the opposite, pumpkins start vs pumpkins start --no-create.

  • We could solve this by separating the commands: pumpkins create pumpkins start

  • We could solve this by separating create flow into own package, aligning with https://docs.npmjs.com/cli/init / https://yarnpkg.com/lang/en/docs/cli/create.

  • We could solve this with a hybrid solution:

    yarn global add pumpkins   <-- pre-req
    
    pumpkins create
    pumpkins start --create
    

    yarn create pumpkins
    npm init pumpkins
    

I think the hybrid approach is best. create-pumpkins package would largely be the same code powering pumpkins create and pumpkins start --create.

[jasonkuhrt]

Since shipped