naro-mcp 0.9.0 → 0.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/dist/index.js +2 -2
  3. package/package.json +4 -4
package/README.md CHANGED
@@ -65,7 +65,7 @@ Headless/CI agents can skip `naro login` and set a token instead:
65
65
  | `cancel_deployment` | Stops a build that is still running (QUEUED–BUILDING). Does not undo a deployment that already went live — use `rollback_deployment` for that |
66
66
  | `enable_database`, `get_database`, `list_tables` | The project's D1 database: turn it on, status/size/limits, schema (verbose: true for columns, indexes and foreign keys) |
67
67
  | `execute_sql` | Run SQL (argument `query`, optional `params` for a single statement; several statements run as one transaction). Destructive; under `--read-only` it stays but accepts a single read statement only |
68
- | `apply_migration`, `list_migrations`, `generate_typescript_types` | Numbered migrations in the `d1_migrations` ledger wrangler also uses (each file all-or-nothing), and TypeScript types for the schema (text only; its `Database` is what `createClient<Database>()` from `@naro/sdk` takes) |
68
+ | `apply_migration`, `list_migrations`, `generate_typescript_types` | Numbered migrations in the `d1_migrations` ledger wrangler also uses (each file all-or-nothing), and TypeScript types for the schema (text only; its `Database` is what `createClient<Database>()` from `naro-js` takes) |
69
69
  | `create_table`, `alter_table`, `drop_table`, `create_index`, `drop_index` | Schema changes without SQL: naro renders checked DDL, applies it as one numbered migration (`NNNN_schema_<op>_<table>.sql`) and writes the file like `apply_migration`. `alter_table` adds, renames or drops a column or renames the table. Dropping a table or column needs `confirm`; `alter_table`, `drop_table` and `drop_index` are destructive and hidden under `--read-only`. `dryRun: true` returns the SQL only |
70
70
  | `export_database` | SQL dump of the database (`schemaOnly`, `dataOnly`, `tables`): waits up to 5 minutes and returns a signed download link plus `atBookmark`, the point the dump reflects |
71
71
  | `restore_database` | Time Travel restore to a `bookmark` or a `timestamp` (last 30 days). Destructive; hidden under `--read-only`. Returns `previousBookmark`, which undoes it |
package/dist/index.js CHANGED
@@ -17397,7 +17397,7 @@ var DATABASE_TOOLS = [
17397
17397
  destructiveHint: false,
17398
17398
  idempotentHint: true
17399
17399
  },
17400
- description: `Generates TypeScript types for the D1 schema: one Row interface per table and view, a Database type with Row, Insert and Update per table that createClient<Database>() from @naro/sdk reads, the Tables, TablesInsert and TablesUpdate helpers, and an Env with the DB binding. Returns the text only \u2014 write it to a file yourself (for example src/database.types.ts). A view that could not be described is an empty interface in the text and is named under the undescribed key. Where the backend's insert rule for a table is owner, its owner column is optional in Insert (the backend fills it); when the policies cannot be read, the result says policies: "unavailable" with policiesReason, and the owner columns stay required. ${UNTRUSTED}`,
17400
+ description: `Generates TypeScript types for the D1 schema: one Row interface per table and view, a Database type with Row, Insert and Update per table that createClient<Database>() from naro-js reads, the Tables, TablesInsert and TablesUpdate helpers, and an Env with the DB binding. Returns the text only \u2014 write it to a file yourself (for example src/database.types.ts). A view that could not be described is an empty interface in the text and is named under the undescribed key. Where the backend's insert rule for a table is owner, its owner column is optional in Insert (the backend fills it); when the policies cannot be read, the result says policies: "unavailable" with policiesReason, and the owner columns stay required. ${UNTRUSTED}`,
17401
17401
  inputSchema: { type: "object", properties: { ...PROJECT_ARGS } },
17402
17402
  handler: async (args, deps) => {
17403
17403
  assertProjectArgs(args);
@@ -18339,7 +18339,7 @@ function toolErrorJson(error51) {
18339
18339
  }
18340
18340
 
18341
18341
  // src/server.ts
18342
- var SERVER_VERSION = "0.9.0";
18342
+ var SERVER_VERSION = "0.9.1";
18343
18343
  function visibleTools(options2) {
18344
18344
  const { features, readOnly } = options2;
18345
18345
  return TOOLS.flatMap((tool) => {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "naro-mcp",
3
- "version": "0.9.0",
3
+ "version": "0.9.1",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "naro-mcp": "./dist/index.js"
@@ -18,15 +18,15 @@
18
18
  "dependencies": {
19
19
  "@modelcontextprotocol/sdk": "^1.0.0",
20
20
  "@supabase/supabase-js": "2.112.3",
21
- "naro-cli": "0.9.0"
21
+ "naro-cli": "0.9.1"
22
22
  },
23
23
  "devDependencies": {
24
24
  "tsup": "8.5.0",
25
25
  "tsx": "4.23.12",
26
26
  "typescript": "7.0.2",
27
27
  "vitest": "3.2.7",
28
- "@next-deploy/config": "0.1.0",
29
- "@next-deploy/sdk": "0.1.0"
28
+ "@next-deploy/sdk": "0.1.0",
29
+ "@next-deploy/config": "0.1.0"
30
30
  },
31
31
  "scripts": {
32
32
  "build": "tsup",