@lightdash/cli 1.65.1 → 1.67.0

package/dist/handlers/apps/scaffolding.test.js

@@ -79,6 +79,17 @@ describe('buildStaticAuthoringFiles', () => {
         expect(text('.npmrc')).toContain('ignore-scripts=true');
         expect(text('.npmrc')).not.toContain('shamefully-hoist');
     });
+    it('classifies local build failures as non-blocking warnings', () => {
+        for (const path of [
+            'README.md',
+            'AGENTS.md',
+            '.claude/skills/developing-data-apps-locally/SKILL.md',
+        ]) {
+            expect(text(path)).toContain('non-blocking warning');
+            expect(text(path)).toContain('continue to upload');
+            expect(text(path)).toContain('server build');
+        }
+    });
     it('never writes app source (no src/ files)', () => {
         expect(files.every((f) => !f.path.startsWith('src/'))).toBe(true);
     });

package/dist/vendor/authoring/AGENTS.md.tmpl

@@ -6,7 +6,7 @@ Two skills in `.claude/skills/` describe how to edit this app:
 
 Edit only `src/`. Root config files are read-only reference — the server rebuilds against a trusted template.
 
-The local build is an optional pre-check. Apps made with `lightdash apps create` already have dependencies installed and can run `npm run build`; after `lightdash download`, use `npm install && npm run build` if you choose to build locally. If install fails, skip it and upload — never modify machine config, npmrc, or dependency files to force it; the server rebuild is authoritative.
+The local build is an optional pre-check. Apps made with `lightdash apps create` already have dependencies installed and can run `npm run build`; after `lightdash download`, use `npm install && npm run build` if you choose to build locally. If the local install or build fails, report it as a non-blocking warning with a short failure summary, then continue to upload — never modify machine config, npmrc, or dependency files to force it. The local pre-check does not decide whether the app ships; the server build is authoritative and surfaces its result on the app page.
 
 Build with the template's preinstalled dependency set (see `package.json`). Adding new npm packages only works when the Lightdash organization has custom dependencies enabled — assume it does not; ask the user before considering a new library, and never vendor library source into `src/` as a workaround. Where enabled, adding a dependency is the one workflow that still requires pnpm: upload requires a matching `pnpm-lock.yaml`, so `pnpm add <pkg>` (or `pnpm install --lockfile-only`) must succeed locally. If it fails, stop and report the error — hand-editing `package.json` without the lockfile makes the upload fail.
 

package/dist/vendor/authoring/README.md.tmpl

@@ -4,7 +4,7 @@ Created or downloaded with the Lightdash CLI.
 
 ## Edit → build → upload
 1. Edit files under `src/`.
-2. Optionally, run `npm run build` to check it compiles locally. `lightdash apps create` installs the initial dependencies after asking permission; after `lightdash download`, run `npm install` first if `node_modules` is absent. If install fails in your environment, skip the local build — the server build on upload is authoritative and surfaces errors on the app page. Don't change machine or registry config to force it.
+2. Optionally, run `npm run build` to check it compiles locally. `lightdash apps create` installs the initial dependencies after asking permission; after `lightdash download`, run `npm install` first if `node_modules` is absent. If the local install or build fails in your environment, treat it as a non-blocking warning and continue to upload. Keep the failure details because they may predict a server build problem, but don't change machine or registry config to force the pre-check to pass — the server build on upload is authoritative and surfaces its result on the app page.
 3. Optionally, preview against real data: `lightdash apps preview` (needs a successful `npm install`).
 4. `lightdash upload --apps <slug>` (the `slug` from `lightdash-app.yml`) — Lightdash rebuilds and serves the app.
 

package/dist/vendor/authoring/developing-data-apps-locally/SKILL.md

@@ -34,6 +34,7 @@ You are editing a Lightdash **data app** that was created or downloaded with the
 ## The local build is optional — never fight a failing install
 
 - If `npm install` fails (registry policy, an unavailable pinned SDK version, no network access), **skip the local build entirely and go straight to upload**. The server rebuild is authoritative and surfaces build errors on the app page.
+- Treat any standard local install or build failure as a **non-blocking warning**, not as an upload error or a failed task. Preserve a short summary of the local failure because it may predict a server build problem, then continue to upload. Make it explicit that the local pre-check did not complete, but that it does not decide whether the app ships; the server build does.
 - Do **not** modify machine configuration, `.npmrc` files, registry settings, or the project's dependency files to force an install to work.
 - A missing `node_modules` is a normal state, not a problem to fix. Never run installs just because it is absent.
 - **Exception — adding a dependency** (only for organizations with custom dependencies enabled — see "Library boundaries" above). This is the one workflow that still requires pnpm: upload rejects new dependencies unless `pnpm-lock.yaml` was regenerated to match `package.json`, so dependency resolution MUST succeed locally. Use `pnpm add <pkg>` — prefixed with Socket Firewall when available (`sfw pnpm add <pkg>`; check with `command -v sfw`) to block known-malicious packages — or after editing `package.json` run `pnpm install --lockfile-only` (updates the lockfile without installing). If resolution fails, **stop and report the exact pnpm error to the user** — never hand-edit `package.json` and proceed without the lockfile; the upload will fail.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.65.1",
+  "version": "1.67.0",
   "description": "Lightdash CLI tool",
   "license": "MIT",
   "repository": {
@@ -41,8 +41,8 @@
     "unique-names-generator": "4.7.1",
     "uuid": "11.1.1",
     "yaml": "2.8.3",
-    "@lightdash/common": "1.65.1",
-    "@lightdash/warehouses": "1.65.1"
+    "@lightdash/warehouses": "1.67.0",
+    "@lightdash/common": "1.67.0"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",