Copy templates into CLI dist folder

[jplhomer]

Our H2 CLI is kinda tricky to use today. It's an oclif plugin which is meant to be executed by npx @shopify/hydrogen the official CLI, which requires you to install it as a plugin (and then remember to uninstall it for localdev).

It's also super clunky trying to init a template. Because our repo is not open-source, it requires a GitHub token argument, and then you have to hunt down that token.

Instead, as a temporary workaround, I've done the following:

• Temporarily build templates into cli dist folder
• Create temporary executable to init app using a dist template

After publishing, this means creating a new H2 app will be as easy as:

# Use default `demo-store` template
npx @shopify/cli-h2-test

# Use a different template
npx @shopify/cli-h2-test /path/to/npx/cli/dist/templates/hello-world

This also makes it trivial to share our progress with external parties without granting them access to our GitHub repos.

We can throw all of this code away once we're open source 👍

[frandiox]

Terrific idea, Josh! 🎸

[frandiox]

Only moving the TS versions because the CLI can already generate JS versions on the fly using Remix, right?

[jplhomer]

Yep. We only really need to generate the JS versions for use in Oxygen Admin or StackBlitz

[frandiox]

TIL using URL this way for local paths 💯

[frandiox]

@jplhomer Random thought: perhaps can keep this binary executable in the long run instead of having it as temporary?
npx @shopify/cli-hydrogen init would always have value because you don't need to install the main CLI and the plugin beforehand just to create the project, right? Otherwise we need to create a new package for this same purpose.

[frandiox]

Do we need shebang here?

[jplhomer]

I don't think so, as I believe calling a bin file from NPM will likely call it as node <FILE>. Gonna be a little bit of trial and error here, though.