@lenne.tech/cli 1.48.0 → 1.50.0

package/build/templates/nest-server-starter/README.md.ejs

@@ -91,14 +91,21 @@ JavaScript file: src/main.ts
 see [Debug.run.xml](.run/Debug.run.xml)
 
 
-## Test & debug the NestServer package in this project
-Use [yalc](https://github.com/wclr/yalc) to include the NestJS server in the project.
+<% if (props.vendor) { -%>
+## Working on the framework core
+This project runs in vendor mode: the `@lenne.tech/nest-server` core is part of the source tree under `src/core/`, not an npm package, so there is nothing to link.
+
+- Read `src/core/VENDOR.md` first. It records the upstream baseline and every local change to the core.
+- Put project-specific code outside `src/core/`: extend, inherit from or override the core, never patch it for one project.
+- Pull in upstream changes with `/lt-dev:backend:update-nest-server-core`, and propose generally useful core fixes upstream with `/lt-dev:backend:contribute-nest-server-core`.
 
-1. clone [NestServer](https://github.com/lenneTech/nest-server): `git clone https://github.com/lenneTech/nest-server.git`
-2. go to the nest-server folder (`cd nest-server`), install the packages via `npm i` and start the nest server in watch & yalc mode: `npm run watch`
-3. link the nest server live package to this project via `npm run link:nest-server` and start the server: `npm start`
-4. unlink the nest-server live package and use the normal package again when you are done: `npm run unlink:nest-server`
+<% } else { -%>
+## Test & debug the NestServer package in this project
+1. Clone [NestServer](https://github.com/lenneTech/nest-server): `git clone https://github.com/lenneTech/nest-server.git`
+2. Link it into this project with `pnpm run link:nest-server` and start the server: `pnpm start`
+3. Switch back to the published package when you are done: `pnpm run unlink:nest-server`
 
+<% } -%>
 ## Deployment with deploy.party
 
 This project is prepared for deployment with deploy.party.

package/docs/commands.md

@@ -663,29 +663,33 @@ Run `--explain` to see three commonly recommended keys the profile deliberately
 
 ### `lt dev test`
 
-One-shot E2E wrapper: ensure `up`, wait for the App URL, run `pnpm run test:e2e` with the `.lt-dev/.env` bridge loaded. Optional teardown after.
+One-shot E2E wrapper: brings up an isolated test stack next to the `lt dev up` session (own URLs `<slug>-test.localhost` / `api.<slug>-test.localhost`, own ports, own Caddy block, own database `<…>-test`), runs `test:e2e` against it, and tears the stack down afterwards. The dev session is never touched.
 
 **Usage:**
 ```bash
-lt dev test                      # App E2E (projects/app)
-lt dev test --api                # API E2E (projects/api) — no Caddy required
-lt dev test --teardown           # plus `lt dev down` after
+lt dev test                      # App E2E against the isolated stack, auto teardown
+lt dev test --keep               # leave the test stack up afterwards
+lt dev test down                 # tear a leftover test stack down
+lt dev test --api                # API E2E (projects/api) — no stack, no Caddy
 lt dev test --debug              # PWDEBUG=1 + HEADED=1
+lt dev test --shard [N|auto]     # split across N isolated stacks (bare --shard = 2)
 lt dev test -- --ui spec.ts      # everything after `--` is forwarded to playwright
 ```
 
 **Alias:** `lt d t`
 
-**Behaviour:**
-1. Pre-flight: Caddy installed + daemon running (App mode only).
-2. If no `lt dev up` session is alive: invokes `lt dev up` first.
-3. Waits up to 30 s for the App URL to respond.
-4. Reads `<root>/.lt-dev/.env` and merges into the spawn env (existing process.env wins for keys it defines).
-5. Spawns `pnpm run test:e2e [forwarded args]` in `projects/api` (with `--api`) or `projects/app` (default).
-6. With `--teardown`, runs `lt dev down` after.
+**Behaviour (App mode):**
+1. Pre-flight: Caddy installed + daemon running, and `playwright.config.ts` env-aware (otherwise abort; `--force` overrides).
+2. Builds the API and applies pending migrations to the test DB (`migrate:up`, with the API's own env, so it hits the same DB). A failed migration aborts the run; a project without a `migrate:up` script starts unmigrated. Then starts the compiled API. Without a build output it falls back to the project's `start` script, which migrates by itself.
+3. Builds the App (`nuxt build`) and serves the Nitro output.
+4. Waits for both to answer and aborts if either never does, so the suite never runs against a dead stack.
+5. Runs `test:e2e [forwarded args]` in the App with the `.lt-dev/.env.test` bridge loaded.
+6. Tears the stack down (processes, Caddy block, env bridge, session file) unless `--keep` is set.
+
+The test DB outlives the run: the CLI never drops it. That is why step 2 migrates it: without the migration the DB drifts behind every environment that does migrate. A project whose Playwright global-setup resets the DB gets it passed as `MONGO_URI`.
 
 **When to use this vs. `pnpm run test:e2e` directly:**
-- Use **`lt dev test`** for TDD loops, ad-hoc reproduction, or when you want a single-command "ensure-up + run + teardown" flow.
+- Use **`lt dev test`** for TDD loops, ad-hoc reproduction, or when you want a single-command "isolated stack + run + teardown" flow.
 - Use **direct `pnpm run test:e2e`** (or VS Code Playwright Extension, IDE test runners) for everyday work — the auto-injected `playwright.config.ts` bridge loads the `.lt-dev/.env` automatically, so the env is correct without the wrapper.
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lenne.tech/cli",
-  "version": "1.48.0",
+  "version": "1.50.0",
   "description": "lenne.Tech CLI: lt",
   "keywords": [
     "lenne.Tech",
@@ -134,6 +134,9 @@
     "rootDir": "__tests__",
     "testTimeout": 60000,
     "workerIdleMemoryLimit": "512MB",
+    "setupFilesAfterEnv": [
+      "<rootDir>/support/signal-guard.ts"
+    ],
     "testMatch": [
       "<rootDir>/*.test.ts"
     ],

package/build/lib/strip-comments.js

@@ -1,78 +0,0 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
-    Object.defineProperty(o, "default", { enumerable: true, value: v });
-}) : function(o, v) {
-    o["default"] = v;
-});
-var __importStar = (this && this.__importStar) || (function () {
-    var ownKeys = function(o) {
-        ownKeys = Object.getOwnPropertyNames || function (o) {
-            var ar = [];
-            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
-            return ar;
-        };
-        return ownKeys(o);
-    };
-    return function (mod) {
-        if (mod && mod.__esModule) return mod;
-        var result = {};
-        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
-        __setModuleDefault(result, mod);
-        return result;
-    };
-})();
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.stripComments = stripComments;
-const ts = __importStar(require("typescript"));
-/**
- * Removes comments from TypeScript/JavaScript source, preserving everything else verbatim.
- *
- * Exists because detectors that search source for import specifiers must not read comments as
- * code. A keyword-anchored regex is not sufficient on its own: a docblock that DOCUMENTS an import
- * rewrite legitimately quotes the exact syntax the detector looks for. nest-server-starter's
- * `tests/unit/bootstrap-diagnostics.spec.ts` contains
- *
- *   * CLI's vendor conversion rewrites `from '@lenne.tech/nest-server'` to a relative `./core` path
- *
- * which matched `/(?:from|import|…)\s*['"]@lenne\.tech\/nest-server['"]/` and made
- * `lt fullstack init --framework-mode vendor` warn about imports that file does not have.
- *
- * Uses the TypeScript scanner rather than a regex, so string literals, template literals and
- * regex literals containing `//` or `/*` are handled correctly by construction — a hand-rolled
- * stripper trips over `'https://…'` and over `/* ` inside a string.
- *
- * Comment characters are replaced with spaces instead of being deleted, so byte offsets and line
- * numbers of the surrounding code stay unchanged — a caller can still report a meaningful
- * position from a match.
- *
- * @param source - TypeScript or JavaScript source text
- * @returns The source with every comment blanked out
- *
- * @example
- * stripComments("// from 'pkg'\nimport x from 'pkg';")
- * // => "             \nimport x from 'pkg';"
- */
-function stripComments(source) {
-    const scanner = ts.createScanner(ts.ScriptTarget.Latest, /* skipTrivia */ false, ts.LanguageVariant.Standard, source);
-    let result = '';
-    let token = scanner.scan();
-    while (token !== ts.SyntaxKind.EndOfFileToken) {
-        const text = scanner.getTokenText();
-        const isComment = token === ts.SyntaxKind.SingleLineCommentTrivia || token === ts.SyntaxKind.MultiLineCommentTrivia;
-        // Keep newlines so line numbers survive; blank everything else in the comment.
-        result += isComment ? text.replace(/[^\n]/g, ' ') : text;
-        token = scanner.scan();
-    }
-    return result;
-}