@lenne.tech/cli 1.15.0 → 1.17.0

package/build/commands/fullstack/init.js

@@ -27,7 +27,7 @@ const NewCommand = {
         // Info
         info('Create a new fullstack workspace');
         // Hint for non-interactive callers (e.g. Claude Code)
-        toolbox.tools.nonInteractiveHint('lt fullstack init --name <name> --frontend <nuxt|angular> --api-mode <Rest|GraphQL|Both> --framework-mode <npm|vendor> [--framework-upstream-branch <ref>] [--next] [--dry-run] --noConfirm');
+        toolbox.tools.nonInteractiveHint('lt fullstack init --name <name> --frontend <nuxt|angular> --api-mode <Rest|GraphQL|Both> --framework-mode <npm|vendor> [--framework-upstream-branch <ref>] [--next: implies nuxt-base-starter#next unless --frontend-branch overrides] [--dry-run] --noConfirm');
         // Check git
         if (!(yield git.gitInstalled())) {
             return;
@@ -264,7 +264,12 @@ const NewCommand = {
         }
         // Determine branches and copy/link paths with priority: CLI > config
         const apiBranch = cliApiBranch || configApiBranch;
-        const frontendBranch = cliFrontendBranch || configFrontendBranch;
+        // Under `--next`, default the nuxt-base-starter ref to the `next`
+        // branch — that branch ships an auth basePath (`/api/auth`) that
+        // matches the experimental nest-base API. Explicit
+        // `--frontend-branch` (or lt.config) still wins so consumers can
+        // target a custom branch on either line.
+        const frontendBranch = cliFrontendBranch || configFrontendBranch || (experimental ? 'next' : undefined);
         const apiCopy = cliApiCopy || configApiCopy;
         const apiLink = cliApiLink || configApiLink;
         const frontendCopy = cliFrontendCopy || configFrontendCopy;
@@ -472,6 +477,39 @@ const NewCommand = {
                 serverSpinner.fail(`Failed to set up API: ${apiResult.path}`);
                 return;
             }
+            // Auto-run `bun run rename <projectDir>` for the experimental nest-base
+            // template. The template ships with hard-coded `nest-base` references in
+            // four files (package.json, README.md, portless.yml, docker-compose.yml).
+            // The rename script patches all four idempotently. Since the consumer
+            // already gave us --name, doing this for them is strictly less
+            // friction-prone than relying on a manual follow-up step (which agents
+            // and humans both forget). Failure is non-fatal: the workspace is still
+            // usable, the user can re-run `bun run rename <name>` manually.
+            //
+            // Note: setupServerForFullstack already patched projects/api/package.json
+            // to set `name = projectDir`. The rename planner reads that name as the
+            // "old" slug, which would short-circuit the README/portless/compose
+            // rewrites because they still say `nest-base`. We restore the canonical
+            // `name = "nest-base"` first so the planner has a coherent starting
+            // state across all four files; the rename then writes the project name
+            // into every spot consistently.
+            if (experimental && apiResult.method !== 'link') {
+                const apiPackageJsonPath = `${apiDest}/package.json`;
+                if (filesystem.exists(apiPackageJsonPath)) {
+                    yield patching.update(apiPackageJsonPath, (config) => {
+                        config.name = 'nest-base';
+                        return config;
+                    });
+                }
+                const renameSpinner = spin(`Rename nest-base → ${projectDir}`);
+                try {
+                    yield system.run(`cd ${apiDest} && bun run rename ${projectDir}`);
+                    renameSpinner.succeed(`Renamed nest-base → ${projectDir} in projects/api`);
+                }
+                catch (err) {
+                    renameSpinner.warn(`Auto-rename failed (${err.message}). Run \`bun run rename ${projectDir}\` manually inside projects/api.`);
+                }
+            }
             // Create lt.config.json for API
             // Note: frameworkMode is persisted under meta so that subsequent `lt
             // server module` / `addProp` / `permissions` calls can detect the mode

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lenne.tech/cli",
-  "version": "1.15.0",
+  "version": "1.17.0",
   "description": "lenne.Tech CLI: lt",
   "keywords": [
     "lenne.Tech",