@goldencomm/create-baseline

Scaffolds a standalone project from a Baseline template — copies the template, then rewires it into its own project (names, README, the design-system deps, and platform-specific fixups). Zero dependencies; Node built-ins only.

Usage

Standalone (npm)

Because the package is named @goldencomm/create-baseline, npm's create prefix mapping means the exact command is:

npm create @goldencomm/baseline <platform> <name>
# flags need a `--` separator so npm doesn't eat them:
npm create @goldencomm/baseline <platform> <name> -- --dir ../my-app --ds-version ^0.0.1

(pnpm create @goldencomm/baseline … and npx @goldencomm/create-baseline … work too.)

Inside the monorepo

pnpm create-baseline <platform> <name> [options]
# or directly:
node tools/create-baseline/index.mjs <platform> <name> [options]

| Platform | Produces | |---|---| | next | Next.js App Router app (React + ds-core/ds-react) | | shopify | Shopify OS 2.0 theme (vendored baseline.css) | | wordpress | WordPress site scaffold (Composer + DDEV) | | dotnet | (no scaffold) — prints how to consume ds-html + baseline.css (Q-005) |

Options

| Flag | Default | Meaning | |---|---|---| | --dir <path> | ./<name> | Target directory | | --ds-version <ver> | ^0.0.1 | Version pinned for the @goldencomm/ds-* deps | | --force | — | Allow scaffolding into a non-empty directory |

pnpm create-baseline shopify acme-store
pnpm create-baseline next acme-proto --dir ../acme-proto --ds-version ^0.1.0
pnpm create-baseline wordpress acme-site

What it does

1. Copies the template. Two auto-detected source modes:
   • monorepo — inside the design-system repo it copies the committed files of baselines/<platform> via git ls-files (so node_modules, dist, .next, .turbo, vendor are excluded automatically);
   • bundled — installed from npm it copies the templates/ snapshot that the prepack script (scripts/bundle-templates.mjs) baked into the package at publish time from the same git ls-files listing. (npm strips .gitignore/ .npmrc/.npmignore from tarballs, so those are stored renamed — _gitignore etc. — and restored on scaffold.)
2. Rewires identifiers: package.json/composer.json name + description, the README title, and the Shopify theme_name.
3. Rewrites DS deps — any workspace:* (@goldencomm/ds-core, ds-react) becomes --ds-version so the project resolves them from npm.
4. Platform fixups:
   • shopify — repoints the dev token-watch at node_modules/@goldencomm/ds-core.
   • wordpress — removes the monorepo bind-mount (.ddev/docker-compose.packages.yaml), adds Composer require + VCS repos for goldencomm/wp-theme and goldencomm/wp-blocks-plugin, renames the DDEV project, and updates seed.sh (theme slug → wp-theme, site host → <name>.ddev.site).

Standalone readiness

• Shopify — works now; baseline.css is vendored into assets/.
• Next — needs @goldencomm/ds-core + ds-react on npm before npm install resolves (they ship at 0.0.1).
• WordPress — goldencomm/wp-theme + wp-blocks-plugin are not published as Composer packages yet; composer install currently requires monorepo/Bitbucket VCS access and your own gitignored auth.json for the ACF/Gravity/Bitbucket credentials (never copied by the scaffolder). The scaffolder prints this caveat.

Publishing notes

• templates/ is generated by prepack and gitignored — never commit it; it is rebuilt from the committed baselines on every pnpm pack / npm publish.
• Packing/publishing must therefore happen from a monorepo checkout (prepack runs git ls-files).