@rebasepro/cli 0.19.1 → 0.19.2-canary.g08eed46

package/dist/index.es.js

@@ -1653,7 +1653,7 @@ function buildInitQuestions(params) {
 		type: "input",
 		name: "projectName",
 		message: "Project name:",
-		default: "my-rebase-app",
+		default: "my-app",
 		validate: (input) => validateProjectName(input) ?? true
 	});
 	if (headlessArg === void 0) questions.push({
@@ -1721,7 +1721,7 @@ ${chalk.bold("Usage")}
   rebase init ${chalk.blue("[name]")} [options]
 
   ${chalk.gray("The name may be a nested path (apps/my-app) or \".\" for the current directory.")}
-  ${chalk.gray("Defaults to \"my-rebase-app\" when omitted with --yes.")}
+  ${chalk.gray("Asks when omitted; defaults to \"my-app\", and takes it without asking under --yes.")}
 
 ${chalk.bold("Options")}
   ${chalk.blue("-t, --template")} ${chalk.gray("<preset>")}   blog | ecommerce | blank ${chalk.gray("(default: blog)")}
@@ -1803,7 +1803,7 @@ async function promptForOptions(rawArgs, pm) {
 	const installFlag = noInstall ? false : args["--install"] ?? false;
 	const hasInstallFlag = noInstall || args["--install"] === true;
 	if (isNonInteractive) {
-		const projectName = nameArg || "my-rebase-app";
+		const projectName = nameArg || "my-app";
 		const targetDirectory = path.resolve(process.cwd(), projectName);
 		const templateDirectory = path.resolve(cliRoot, "templates", "template");
 		const pmCommands = getPMCommands(pm);
@@ -5486,11 +5486,17 @@ function projectHasCollections(projectRoot) {
 * Boot created all 30 tables through the additive ensure, `/health` answered
 * 200, auth worked, the admin panel loaded — and every single
 * `GET /api/data/*` returned a 500, `Table not found for collection 'posts'`,
-* because the driver looks the table up in the generated file rather than in the
-* database. A stranger following the README had no way to guess that
+* because the driver looked the table up in the generated file rather than in
+* the database. A stranger following the README had no way to guess that
 * `pnpm run schema:generate` was the missing step, and the README told them the
 * schema was pushed for them.
 *
+* That failure is fixed at the root — the driver builds its tables from
+* `information_schema` now, so a stub `schema.generated.ts` cannot empty the
+* API. This still runs, because the file is a real artifact for everything
+* around the server: `db push` diffs it, Atlas plans from it, `eject` writes it
+* out, and application code imports it.
+*
 * ## Why it runs unconditionally
 *
 * Generation reads collection files and writes one file. It needs no database,