delacour 0.1.0-alpha.4 → 0.1.0

package/README.md

@@ -5,7 +5,7 @@ repository — you own `button.tsx` and can edit it, rather than waiting for a
 release.
 
 ```bash
-bunx delacour@alpha add button
+bunx delacour@latest add button
 ```
 
 That is the whole install. `add` sets the project up on its first run — config, Metro, the Tailwind
@@ -58,7 +58,7 @@ whether or not any are missing:
 
 ```txt
 ●  Needs 14 external packages, 2 not here yet:
-│    bunx expo install @gorhom/bottom-sheet react-native-keyboard-controller
+│    bunx expo install react-native-teleport react-native-keyboard-controller
 │    already installed — clsx, react-native-reanimated, react-native-svg, tailwind-variants, …
 ```
 
@@ -66,7 +66,7 @@ Then it asks. `--install` answers yes without asking, `--no-install` answers no,
 nobody to ask — a script, CI, an agent — installs nothing and prints the commands instead:
 
 ```bash
-bunx delacour@alpha add bottom-sheet --install
+bunx delacour@latest add bottom-sheet --install
 ```
 
 The missing packages are shown as commands, not names, because the command is the part that is not
@@ -86,7 +86,7 @@ import { Button } from "@acme/ui/button";
 ```
 
 ```bash
-bunx delacour@alpha init --package-name @acme/ui --package-path packages/ui   # no prompts
+bunx delacour@latest init --package-name @acme/ui --package-path packages/ui   # no prompts
 ```
 
 
@@ -95,8 +95,8 @@ bunx delacour@alpha init --package-name @acme/ui --package-path packages/ui   #
 walking up from `--cwd`. In a monorepo that means:
 
 ```bash
-cd packages/ui && bunx delacour@alpha init    # shared package, several apps use it
-cd apps/mobile && bunx delacour@alpha init    # straight into the app
+cd packages/ui && bunx delacour@latest init    # shared package, several apps use it
+cd apps/mobile && bunx delacour@latest init    # straight into the app
 ```
 
 Either way the CLI finds the Expo app and wires *its* Metro config and CSS
@@ -158,7 +158,7 @@ a JS reload alone will red-box. `add` says so at the point it becomes true.
 ## Working on this package
 
 ```bash
-bun run registry:build   # rebuild registry/ from packages/native-ui
+bun run registry:build   # rebuild registry/ from packages/react-native-ui
 bun test                 # unit + end-to-end against the local registry
 bun run verify:expo      # scaffold a real Expo app, add everything, typecheck it
 bun run build            # bundle dist/index.js
@@ -226,14 +226,14 @@ watching the check fire.
 `--all` adds components and what they pull in, so the run also names the standalone utilities
 explicitly — a verification pass has to cover the whole registry, not most of it.
 
-The registry is **derived** from `packages/native-ui/src` — one item per
+The registry is **derived** from `packages/react-native-ui/src` — one item per
 component folder, dependencies read off the imports. There is no `registry.json`
 to maintain, and the builder throws rather than guessing: an unclassified npm
 import or a component folder without an `index.ts` fails the build.
 
 It writes `registry.json` (the index), `r/<name>.json` (one item per component,
 naming its files) and the three JSON schemas. It writes **no copy of the
-source**: an item names the library's own file — `packages/native-ui/src/components/button/button.tsx` —
+source**: an item names the library's own file — `packages/react-native-ui/src/components/button/button.tsx` —
 and the client fetches it at the same ref the item came from, so the two cannot
 disagree. A component's diff is therefore the TypeScript that changed rather
 than a JSON string nobody can read.