@rebasepro/cli 0.13.0 → 0.13.1-canary.g394d868

package/dist/telemetry/payload.d.ts

@@ -31,7 +31,7 @@
  */
 export declare const TELEMETRY_SCHEMA_VERSION = 1;
 /** The events the CLI reports. Closed set — a name not listed cannot be sent. */
-export type TelemetryEventName = "cli.init" | "cli.dev" | "cli.deploy" | "cli.schema_generate" | "cli.db_push" | "cli.error";
+export type TelemetryEventName = "cli.init" | "cli.dev" | "cli.deploy" | "cli.schema" | "cli.db" | "cli.error";
 /** A single non-free-text value. */
 export type TelemetryValue = string | number | boolean;
 export type TelemetryEvent = {

package/dist/utils/collection-drift.d.ts

@@ -0,0 +1,27 @@
+/**
+ * Would `loadCollectionsFromDirectory` load this file?
+ *
+ * Mirrors that loader's own `isCollectionFile` plus its flat (non-recursive)
+ * scan. `relativePath` is relative to the collections directory, as `fs.watch`
+ * reports it.
+ */
+export declare function isLoadedCollectionFile(relativePath: string): boolean;
+/**
+ * Does this collection source declare anything a SQL toolchain would own?
+ *
+ * The fallback order matches `resolveDataSource`: an explicit `engine` wins,
+ * and a collection that only names a `dataSource` is resolved as if the key
+ * were the engine — which is what that function does when no registry is
+ * available, and the CLI has none. An engine nobody recognises counts as
+ * relational, for the reason `isRelationalCollection` gives.
+ *
+ * A file declaring several collections is SQL-affecting if *any* of them is.
+ */
+export declare function declaresRelationalCollection(rawSource: string): boolean;
+/**
+ * Can this edit have changed the generated SQL schema?
+ *
+ * Answers `true` when it cannot tell — an unreadable file is a reason to warn,
+ * not a reason to go quiet.
+ */
+export declare function affectsSqlSchema(collectionsDir: string, relativePath: string): boolean;

package/dist/utils/project.d.ts

@@ -34,6 +34,26 @@ export declare function findFrontendDir(projectRoot: string): string | null;
  * Find the .env file. Checks the project root first, then backend.
  */
 export declare function findEnvFile(projectRoot: string): string | null;
+/**
+ * Read the project's `.env` into a plain object.
+ *
+ * One reader, because there were four: `dotenv` in `start`, a hand-rolled
+ * `indexOf("=")` loop in `api-keys`, a single-key regex in `auth`, and its own
+ * splitting in `cloud env`. `dotenv` is a declared dependency of this package,
+ * so the other three existed for no reason and disagreed with the correct one
+ * on the two things people actually write in a `.env`:
+ *
+ *   - `export KEY=value`, which the hand-rolled parser keyed as
+ *     `export KEY` — so the command reported the key as unset while it was
+ *     right there in the file;
+ *   - `KEY=value # comment`, whose comment travelled into the value and then
+ *     into an `Authorization` header, coming back as a 401 with nothing
+ *     pointing at the cause.
+ *
+ * Returns `{}` when the project has no `.env`, so callers can treat "absent"
+ * and "empty" alike.
+ */
+export declare function readEnvFile(projectRoot: string): Record<string, string>;
 /**
  * Resolve a binary from the project's node_modules/.bin.
  * Checks backend, root, parent monorepo root, then falls back to PATH.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebasepro/cli",
-  "version": "0.13.0",
+  "version": "0.13.1-canary.g394d868",
   "description": "Developer tools for Rebase projects",
   "main": "./dist/index.es.js",
   "module": "./dist/index.es.js",
@@ -31,12 +31,12 @@
     "execa": "^9.6.1",
     "inquirer": "14.0.2",
     "jiti": "^2.7.0",
-    "@rebasepro/agent-skills": "0.13.0",
-    "@rebasepro/client": "0.13.0",
-    "@rebasepro/codegen": "0.13.0",
-    "@rebasepro/types": "0.13.0",
-    "@rebasepro/server": "0.13.0",
-    "@rebasepro/server-postgres": "0.13.0"
+    "@rebasepro/agent-skills": "0.13.1-canary.g394d868",
+    "@rebasepro/codegen": "0.13.1-canary.g394d868",
+    "@rebasepro/client": "0.13.1-canary.g394d868",
+    "@rebasepro/server": "0.13.1-canary.g394d868",
+    "@rebasepro/server-postgres": "0.13.1-canary.g394d868",
+    "@rebasepro/types": "0.13.1-canary.g394d868"
   },
   "devDependencies": {
     "@types/node": "^26.1.2",

package/templates/template/config/package.json

@@ -16,6 +16,7 @@
     "@rebasepro/types": "workspace:*"
   },
   "devDependencies": {
+    "@types/node": "^20.19.41",
     "typescript": "^5.9.2"
   },
   "exports": {