-
Notifications
You must be signed in to change notification settings - Fork 627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI - init command #380
Comments
Second thoughts: scope is too broad. The
|
Sample usage:
Where app is a "registered" metalsmith starter. "Registered" means as much as "committed to a source file in the package".
The command should:
.
the default destinationgit clone --depth=1
command, see also: https://www.systutorials.com/how-to-clone-a-snapshot-of-a-remote-repository-at-a-specific-branch/. This stays true to metalsmith's simplicity and avoids relying on OS-specific/optional soft (like unzip/curl etc) and offers a DX as good asnpx @org/pkg
without requiring NPM (which brings its own share of trouble, ie what if the used pkg mgr is yarn or pnpm?)git clone --depth=1
command, see also: https://www.systutorials.com/how-to-clone-a-snapshot-of-a-remote-repository-at-a-specific-branch/. This stays true to metalsmith's simplicity and avoids relying on OS-specific/optional soft (like unzip/curl etc) and offers a DX as good asnpx @org/pkg
without requiring NPM (which brings its own share of trouble, ie what if the used pkg mgr is yarn or pnpm?)npm i <author>/<repo>
which involves text parsing, or with an alias registry (similar to metalsmith.io's plugin registry).It would be nice to have a signature like
metalsmith create company-website
&metalsmith create
basic/express-app&
metalsmith create:namespace/portfolio|resume
The text was updated successfully, but these errors were encountered: