naro-cli 0.9.0 → 0.9.1

package/README.md

@@ -112,7 +112,7 @@ naro migration repair 0001_init.sql --status applied
                                    reverted to drop its row. Its SQL is never run
 naro gen types --output src/database.types.ts
                                    TypeScript types for the schema, for
-                                   createClient<Database>() from @naro/sdk
+                                   createClient<Database>() from naro-js
 
 naro backend status                On or off, status, URL and anon key (service key hidden)
 naro backend enable                Turn the backend on: D1, sign-in and the Data API; safe
@@ -241,7 +241,7 @@ says what you asked for, it says so and writes nothing.
 
 `naro gen types` writes TypeScript for the schema: a `…Row` interface per
 table and view, and a `Database` type that `createClient<Database>()` from
-`@naro/sdk` reads, with `Tables<"name">`, `TablesInsert<"name">` and
+`naro-js` reads, with `Tables<"name">`, `TablesInsert<"name">` and
 `TablesUpdate<"name">` to pick one out. `--lang typescript` is the default and
 the only language.
 
@@ -250,7 +250,7 @@ naro gen types --output src/database.types.ts
 ```
 
 ```ts
-import { createClient } from "@naro/sdk";
+import { createClient } from "naro-js";
 import type { Database } from "./database.types";
 
 const naro = createClient<Database>({ url, anonKey });
@@ -273,7 +273,7 @@ and BLOB was `ArrayBuffer`: use `Tables<"users">` now. The `…Row` interfaces
 are unchanged.
 
 `naro backend` is the project's Naro backend: its own D1, email and password
-sign-in, and a Data API that browser code calls through `@naro/sdk` at the
+sign-in, and a Data API that browser code calls through `naro-js` at the
 project's URL. It is off until you turn it on, one project at a time:
 `naro backend enable` (or the Database page of the dashboard). The anon key
 is public — it identifies the project and grants nothing. The service key
@@ -362,7 +362,7 @@ the generated `Insert` even when it is `NOT NULL` with no default — run it
 again after changing a policy.
 
 Instead of a rule, an action can hold a condition on the row, like a Supabase
-row-level security policy, written in the filter syntax of `@naro/sdk`'s
+row-level security policy, written in the filter syntax of `naro-js`'s
 `.or()` (commas are AND) with `auth.uid()` for the signed-in user's id —
 unquoted; `"auth.uid()"` is the text, and `auth.uid` without `()` is refused
 rather than read as text:

package/dist/index.js

@@ -4179,7 +4179,7 @@ Usage:
        --status applied|reverted [--yes]  remove its row. Its SQL is never run (asks first)
   naro gen types [--lang typescript] [--output <file>]
                                      TypeScript types for the schema, for createClient<Database>()
-                                     from @naro/sdk (stdout by default)
+                                     from naro-js (stdout by default)
 
   naro backend [status]              On or off, status, URL and anon key (the service key stays hidden)
   naro backend enable                Turn the backend on: D1, sign-in and the Data API (safe to re-run;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "naro-cli",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "type": "module",
   "bin": {
     "naro": "./dist/index.js"
@@ -33,11 +33,11 @@
     "tsx": "4.23.12",
     "typescript": "7.0.2",
     "vitest": "3.2.7",
-    "@naro/sdk": "0.1.0",
+    "naro-js": "0.1.0",
     "@next-deploy/build": "0.1.0",
+    "@next-deploy/core": "0.1.0",
     "@next-deploy/config": "0.1.0",
     "@next-deploy/data-core": "0.1.0",
-    "@next-deploy/core": "0.1.0",
     "@next-deploy/sdk": "0.1.0"
   },
   "scripts": {