@shop-on/create-theme 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shop-on/create-theme",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Scaffolds a Shop-On storefront theme: `npm create @shop-on/theme <dir>`.",
   "license": "SEE LICENSE IN dist/LICENSE.md",
   "bin": {
@@ -16,9 +16,9 @@
     "./package.json": "./package.json"
   },
   "devDependencies": {
-    "@types/node": "26.6.3",
+    "@types/node": "26.6.5",
     "typescript": "7.0.2",
-    "vitest": "5.0.3"
+    "vitest": "5.0.5"
   },
   "engines": {
     "node": "^20.19.0 || >=22.12.0"
@@ -26,6 +26,6 @@
   "scripts": {
     "template": "node scripts/template.mts",
     "check-types": "tsc --noEmit",
-    "test": "vitest run"
+    "test": "vitest run --maxWorkers=2"
   }
 }

package/template/.claude/skills/theme-dev/SKILL.md

@@ -260,7 +260,7 @@ A theme change is not finished when it type-checks — the artifact carries a ve
 1. Bump `package.json#version` (semver). Fix → patch; new section, block or setting → minor.
 2. Prepend a `## X.Y.Z` section to `release-notes.md`. The platform stores only the section matching the uploaded version, so each one carries its own notes.
 3. `pnpm build` — postbuild emits `.output/theme.json` at the new version, and fails fast if `theme.config.json#locales` omits `"en"`. Check `theme.config.json#locales` matches the catalogs you ship first: a declared locale with no catalog renders default-language copy.
-4. Package. **Don't improvise the tarball.** Two things a hand-rolled `tar` gets wrong: entries must sit **flat at the tarball root** (`-C .output`, pack `.`), and macOS needs `COPYFILE_DISABLE=1` + `--no-mac-metadata` to keep AppleDouble `._*` entries out (drop `--no-mac-metadata` on GNU tar): `COPYFILE_DISABLE=1 tar -czf ../<name>-X.Y.Z.tar.gz -C .output --exclude='.DS_Store' --no-mac-metadata .`. Uploading a version to the theme store isn't open to third-party developers yet; the tarball is as far as this goes for now.
+4. Package. **Don't hand-roll the tarball**: `npx @shop-on/theme-cli theme pack` writes `<name>-X.Y.Z.tar.gz` in the theme directory (`--out <path>` to put it elsewhere, `--build` to build first). Entries sit flat at the root with no macOS metadata, the same on every OS, and it refuses a build missing a file the theme store requires or older than `package.json`. Uploading a version to the theme store isn't open to third-party developers yet; the tarball is as far as this goes for now.
 
 Write the notes **for the merchant, not the diff**: what changes in their store, in their words. Match the file — plain bullets under the heading, no `### Fixed` subsections, no file names, no component names. "Prices now say when tax is included", not "added `taxIncludedCaption` to the price block".
 

package/template/.claude/skills/theme-dev/recipes/dynamic-sources.md

@@ -173,7 +173,7 @@ GID is in place before its `${id}Data` resolver runs:
 1. **Fetch metaobject entries** — `loadMetaobjectFieldSources(template, product)`
    collects the union of pinned entry ids (`collectMetaobjectEntryIds`, binding +
    inline forms) and traversed entry ids (`collectTraversedEntryIds(template,
-product.metafields)` — field-bearing `product_metafield` refs), early-returns
+   product.metafields)` — field-bearing `product_metafield` refs), early-returns
    `{}` when none, else batch-fetches (`fetchMetaobject`, deduped + `memoTTL`-
    cached, capped at 50 with a warning) and builds `{ entry: { key: { type, value } } }`.
 2. **Whole-value pass — BEFORE the picker-data resolvers.**

package/template/.claude/skills/theme-dev/recipes/quality.md

@@ -25,7 +25,7 @@ pnpm build                     # postbuild enforces the build lines
 The output is one line per finding, `file:line rule message`, followed by the
 recipe for each rule that fired.
 
-The **audit** lines come from `shop-on theme audit`, in the `@shop-on/cli`
+The **audit** lines come from `shop-on theme audit`, in the `@shop-on/theme-cli`
 package:
 
 ```bash
@@ -41,7 +41,7 @@ missing instead of measuring an empty page. The password template is left
 out, since it only renders while protection is on, and the audit refuses a
 protected store.
 
-`@shop-on/cli` isn't published yet. Until it is, measure the **audit** lines
+`@shop-on/theme-cli` isn't published yet. Until it is, measure the **audit** lines
 by hand, as each one says.
 
 ## Performance

package/template/README.md

@@ -8,16 +8,16 @@ published `@shop-on/theme-*` packages.
 ## Quick start
 
 ```sh
-npx @shop-on/cli theme init my-theme   # scaffold, log in if needed, write .env, install
+npx @shop-on/theme-cli theme init my-theme   # scaffold, log in if needed, write .env, install
 cd my-theme
-npx @shop-on/cli theme dev             # open this theme in your store's theme editor
+npx @shop-on/theme-cli theme dev             # open this theme in your store's theme editor
 ```
 
 The first time, `theme init` opens your browser on your store's admin:
 approve the CLI and pick the store. Your staff role needs **Manage online store**. It then writes
 `.env` with a storefront credential for that store. `.env` holds secrets:
 never commit it. A store holds at most 5 of these credentials;
-`npx @shop-on/cli theme credentials revoke <client-id>` frees one.
+`npx @shop-on/theme-cli theme credentials revoke <client-id>` frees one.
 
 `theme dev` runs the theme behind a `cloudflared` tunnel (install it first)
 and opens the hosted theme editor on a developer preview of it. Confirm the

package/template/package.json

@@ -17,36 +17,36 @@
   },
   "dependencies": {
     "@bprogress/core": "1.3.4",
-    "@shop-on/i18n": "^0.1.0",
-    "@shop-on/theme-contract": "^0.1.0",
-    "@shop-on/theme-loader": "^0.1.0",
-    "@shop-on/theme-react": "^0.1.0",
-    "@shop-on/theme-routes": "^0.1.0",
-    "@shop-on/theme-runtime": "^0.1.0",
-    "@shop-on/theme-server": "^0.1.0",
-    "@shop-on/theme-system": "^0.1.0",
+    "@shop-on/i18n": "^0.2.0",
+    "@shop-on/theme-contract": "^0.2.0",
+    "@shop-on/theme-loader": "^0.2.0",
+    "@shop-on/theme-react": "^0.2.0",
+    "@shop-on/theme-routes": "^0.2.0",
+    "@shop-on/theme-runtime": "^0.2.0",
+    "@shop-on/theme-server": "^0.2.0",
+    "@shop-on/theme-system": "^0.2.0",
     "@tailwindcss/vite": "4.3.3",
-    "@tanstack/react-router": "1.170.41",
-    "@tanstack/react-start": "1.168.60",
-    "dotenv": "18.0.5",
+    "@tanstack/react-router": "1.170.45",
+    "@tanstack/react-start": "1.169.3",
+    "dotenv": "18.0.8",
     "nitro": "3.0.260903-beta",
-    "react": "19.3.0",
-    "react-dom": "19.3.0",
+    "react": "19.3.1",
+    "react-dom": "19.3.1",
     "tailwindcss": "4.3.3"
   },
   "devDependencies": {
-    "@shop-on/theme-config": "^0.1.0",
-    "@shop-on/theme-dev-host": "^0.1.0",
+    "@shop-on/theme-config": "^0.2.0",
+    "@shop-on/theme-dev-host": "^0.2.0",
     "@spiriit/vite-plugin-svg-spritemap": "7.2.0",
-    "@types/node": "26.6.3",
+    "@types/node": "26.6.5",
     "@types/react": "19.3.0",
     "@types/react-dom": "19.3.0",
-    "@vitejs/plugin-react": "6.1.1",
-    "gql.tada": "1.11.3",
-    "happy-dom": "20.10.6",
-    "oxfmt": "^0.71.0",
+    "@vitejs/plugin-react": "6.1.2",
+    "gql.tada": "1.11.4",
+    "happy-dom": "21.0.4",
+    "oxfmt": "^0.74.0",
     "typescript": "7.0.2",
-    "vite": "8.3.1",
-    "vitest": "5.0.3"
+    "vite": "8.3.5",
+    "vitest": "5.0.5"
   }
 }