This sounds cool, but just wondering what this adds on top of something like npx @frctl/cli new. Would it add support for something like yarn create fractal-app as well without much effort?

Or (and this might be the best approach) - should we drop fractal new and just have the CLI there to serve and build? That's fine by me, as I've not got that far with the CLI yet, and we can still to the templating thing we discussed if we take this approach.

This would just add a npm "industry standard" alias to npx @frctl/cli new. I don't think it's too much for us to maintain, since it would just trigger the new command. Basically how Pattern Lab does the same thing: https://github.com/pattern-lab/patternlab-node/tree/dev/packages/create

should we drop fractal new and just have the CLI there to serve and build?

I'd rather keep only the project scaffolding feature, that's a great thing to easily create a project that just works. As suggested, users could run it without even having to install the CLI globally with npm init or yarn create. I'd rather ditch the global serve/build tasks as they can cause issues when versions mismatches. Those can and should be run per project with dedicated scripts in the package.json.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Would it add support for something like yarn create fractal-app as well without much effort?

By the looks of it, yarn create works the same as npm init, so it would be yarn create @frctl/fractal.