create-react-native-library-template 0.1.3 → 0.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-react-native-library-template",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Scaffold a React Native UI library monorepo: Bun workspaces, Expo, Storybook (web + native), Vitest, Biome and Changesets",
   "license": "MIT",
   "type": "module",

package/template/.changeset/config.json

@@ -7,5 +7,8 @@
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": ["@template/storybook-web", "@template/example"]
+  "ignore": [
+    "@template/storybook-web",
+    "@template/example"
+  ]
 }

package/template/.github/workflows/release.yml

@@ -24,7 +24,6 @@ jobs:
         with:
           bun-version: latest
 
-      # `changeset publish` shells out to npm, which needs Node and registry auth.
       - uses: actions/setup-node@v4
         with:
           node-version: 22
@@ -43,4 +42,4 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/template/AGENTS.md

@@ -87,14 +87,26 @@ implementation. For a component named `Foo`:
 ## Releasing
 
 CI (`.github/workflows/ci.yml`) runs lint, typecheck, tests, build, and Storybook tests on
-every PR. On pushes to `main`, `.github/workflows/release.yml` uses changesets to open/update
-a "Version Packages" PR; merging it versions `@template/ui` and writes its changelog (the
-library itself stays `private`, so `changeset publish` skips it — this is a template repo,
-the library is for scaffolded projects). The Version PR also bumps the scaffolder version;
-the next push to `main` publishes `create-react-native-library-template` to npm (requires
-`NPM_TOKEN`). Scaffolded projects follow the same flow — rename the `@template/*` packages
-to your own npm scope and set `NPM_TOKEN`. Never edit versions in `package.json` or
-`CHANGELOG.md` by hand.
+every PR. Releasing is driven entirely by changesets: on pushes to `main`,
+`.github/workflows/release.yml` opens/updates a "Version Packages" PR; merging it runs
+`changeset version` (bumping versions and writing changelogs) and the next push runs
+`bun run release` (`changeset publish`) to publish to npm. It needs the `NPM_TOKEN` repository
+secret. Never edit versions in `package.json` or `CHANGELOG.md` by hand — write a changeset
+(`bun run changeset`) instead.
+
+What actually publishes differs by context, and the difference is entirely config-driven (same
+workflow both places):
+
+- **This template repo** publishes only the scaffolder (`create-react-native-library-template`).
+  `create/` is a Bun workspace member, so changesets versions it natively. The three
+  `@template/*` packages are `private` **and** listed in the changesets `ignore` array
+  (`.changeset/config.json`), so they are never versioned or published here — they are
+  placeholder code. Write changesets against `create-react-native-library-template`.
+- **Scaffolded projects** publish their library. The scaffolder strips `create` from the
+  root `workspaces`, removes `@template/ui` from the changesets `ignore` array, and drops its
+  `private` flag — so the library releases through this very same workflow once you rename the
+  `@template/*` packages to your own npm scope (update the same `ignore` array) and set `NPM_TOKEN`.
+
 `.github/workflows/deploy-storybook.yml` builds the web Storybook (`storybook/web`) on every
 push to `main` and deploys it to GitHub Pages (repo Settings → Pages → Source: GitHub Actions).
 

package/template/bun.lock

@@ -16,6 +16,13 @@
         "typescript": "^6",
       },
     },
+    "create": {
+      "name": "create-react-native-library-template",
+      "version": "0.1.4",
+      "bin": {
+        "create-react-native-library-template": "index.mjs",
+      },
+    },
     "packages/ui": {
       "name": "@template/ui",
       "version": "0.1.0",
@@ -1049,6 +1056,8 @@
 
     "core-js-compat": ["core-js-compat@3.49.0", "", { "dependencies": { "browserslist": "^4.28.1" } }, "sha512-VQXt1jr9cBz03b331DFDCCP90b3fanciLkgiOoy8SBHy06gNf+vQ1A3WFLqG7I8TipYIKeYK9wxd0tUrvHcOZA=="],
 
+    "create-react-native-library-template": ["create-react-native-library-template@workspace:create"],
+
     "cross-fetch": ["cross-fetch@3.2.0", "", { "dependencies": { "node-fetch": "^2.7.0" } }, "sha512-Q+xVJLoGOeIMXZmbUK4HYk+69cQH6LudR0Vu/pRm2YlU/hDV9CiS0gKUMaWY5f2NeUH9C1nV3bsTlCo0FsTV1Q=="],
 
     "cross-spawn": ["cross-spawn@7.0.6", "", { "dependencies": { "path-key": "^3.1.0", "shebang-command": "^2.0.0", "which": "^2.0.1" } }, "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA=="],

package/template/package.json

@@ -17,7 +17,7 @@
     "storybook": "bun run --cwd storybook/web storybook",
     "storybook:native": "bun run --cwd storybook/native start",
     "changeset": "changeset",
-    "version-packages": "node scripts/version-packages.mjs",
+    "version-packages": "changeset version",
     "release": "bun run build && changeset publish",
     "prepare": "husky"
   },

package/template/packages/ui/package.json

@@ -1,7 +1,6 @@
 {
   "name": "@template/ui",
-  "version": "0.1.5",
-  "private": true,
+  "version": "0.1.0",
   "description": "Reusable React Native UI component library",
   "license": "MIT",
   "repository": {

package/template/packages/ui/CHANGELOG.md

@@ -1,34 +0,0 @@
-# @template/ui
-
-## 0.1.5
-
-### Patch Changes
-
-- 92189ad: Add custom `version-packages` script that bumps the scaffolder version whenever changesets are consumed, so the template repo's release workflow republishes `create-react-native-library-template` alongside library changes. Update AGENTS.md to reflect the flow: only the scaffolder publishes from the template repo; `@template/ui` stays private. No runtime changes to the published package.
-
-## 0.1.4
-
-### Patch Changes
-
-- 2618470: Mark `@template/ui` as `private` so the release workflow no longer tries to publish the placeholder `@template` scope to npm (which 404s). Changesets still versions it and writes its changelog; the template only publishes the `create/` scaffolder. Scaffolded projects publish their library normally once the `@template/*` packages are renamed to your own npm scope and the `NPM_TOKEN` repository secret is set.
-- 4424a60: Remove the `private` flag from `@template/ui` so the release workflow publishes it to npm (the flag was preventing `changeset publish` from touching it). The scaffolder no longer strips it — scaffolded projects get a publishable library by default, which publishes once the scope is renamed and `NPM_TOKEN` is set.
-
-## 0.1.3
-
-### Patch Changes
-
-- a6ba45e: Mark `@template/ui` as `private` so the release workflow no longer tries to publish the placeholder `@template` scope to npm (which 404s). Changesets still versions it and writes its changelog; the template only publishes the `create/` scaffolder. Scaffolded projects that want to publish their library should rename the `@template/*` packages to their own npm scope, remove `"private": true` from `packages/ui/package.json`, and set the `NPM_TOKEN` repository secret.
-- f8a35ba: Add live-demo and npm badges plus a hosted-Storybook/scaffolder description to the repo `README.md`, and wrap those repo-only sections in `template-exclude` markers so scaffolded projects get a clean README without the template's own demo links and package badges. No runtime changes to the published package.
-
-## 0.1.2
-
-### Patch Changes
-
-- 6c594db: Add a husky `pre-commit` hook that runs lint, typecheck, and unit tests before every commit. Hooks install via a `prepare` script on `bun install`, and the setup is included in scaffolded projects (`bun create react-native-library-template`). The scaffolder's "Next steps" now runs `git init` before `bun install` so the hooks install on the first install. No runtime changes to the published package.
-
-## 0.1.1
-
-### Patch Changes
-
-- f77680d: Repo housekeeping: Storybook workspaces moved from `apps/` to `storybook/` (`storybook/web`, `storybook/native`), the web Storybook demo now deploys to GitHub Pages from `main`, and the contributor guide documents the exports-map convention (per-subpath `exports` in `package.json`, no barrel files). No runtime changes to the published package.
-- 98fd966: Remove `.tsx` extensions from relative imports in test and story files — they made `tsc --noEmit` fail with TS5097 since `allowImportingTsExtensions` is not enabled.

package/template/scripts/version-packages.mjs

@@ -1,21 +0,0 @@
-#!/usr/bin/env node
-import { execFileSync } from 'node:child_process';
-import { readFileSync, writeFileSync } from 'node:fs';
-import { dirname, resolve } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
-
-// Run changeset version
-execFileSync('bun', ['run', 'changeset', 'version'], { cwd: root, stdio: 'inherit' });
-
-// Bump the scaffolder version when changesets are consumed. This is a template repo;
-// the scaffolder must republish when template files change. Always bump it: if no changesets
-// existed, the version PR doesn't open and this doesn't run; if changesets exist, they're
-// for template changes and the scaffolder should ship alongside.
-const createPackagePath = resolve(root, 'create/package.json');
-const createPackage = JSON.parse(readFileSync(createPackagePath, 'utf8'));
-const [major, minor, patch] = createPackage.version.split('.').map(Number);
-createPackage.version = `${major}.${minor}.${patch + 1}`;
-writeFileSync(createPackagePath, `${JSON.stringify(createPackage, null, 2)}\n`);
-console.log(`Bumped create-react-native-library-template to ${createPackage.version}`);