@lightdash/cli 1.49.0 → 1.50.1

package/dist/index.js

@@ -8,6 +8,7 @@ const uuid_1 = require("uuid");
 const env_1 = require("./env");
 const error_1 = require("./error");
 const globalState_1 = tslib_1.__importDefault(require("./globalState"));
+const createApp_1 = require("./handlers/apps/createApp");
 const preview_1 = require("./handlers/apps/preview");
 const compile_1 = require("./handlers/compile");
 const connectSnowflake_1 = require("./handlers/connectSnowflake");
@@ -102,6 +103,20 @@ ${styles.bold('Examples:')}
   ${styles.title('⚡')}️lightdash ${styles.bold('deploy')} ${styles.secondary('-- compiles and deploys Lightdash metrics to active project')}
   ${styles.title('⚡')}️lightdash ${styles.bold('login https://lightdash.domain.com')} ${styles.secondary('-- logs in to a Lightdash instance')}
 `);
+const createProgram = commander_1.program
+    .command('create')
+    .description('Creates Lightdash content locally');
+createProgram
+    .command('app <name>')
+    .description('Creates a new data app locally')
+    .option('--description <text>', 'Set the app description', '')
+    .option('--slug <slug>', 'Override the app slug')
+    .option('-p, --path <path>', 'Specify the Lightdash content root (default: ./lightdash)')
+    .option('--project <project uuid>', 'Specify the project the app will use', parseProjectArgument, undefined)
+    .option('-y, --assume-yes', 'approve npm package installation', false)
+    .option('--verbose', undefined, false)
+    .addHelpText('after', `\n${styles.bold('Example:')}\n  ${styles.title('⚡')}️lightdash ${styles.bold('create app "Revenue explorer"')} ${styles.secondary('-- creates ./lightdash/apps/revenue-explorer')}\n`)
+    .action(createApp_1.createAppHandler);
 commander_1.program
     .command('connect-snowflake')
     .description('Connects Lightdash to Snowflake using browser-based SSO')

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

@@ -2,11 +2,11 @@
 
 Two skills in `.claude/skills/` describe how to edit this app:
 - `lightdash-data-app` — the Lightdash SDK surface (querying data, filters, downloads).
-- `developing-data-apps-locally` — the local workflow: edit `src/`, `npm run build`, `lightdash upload --apps <appUuid>` (uuid in `lightdash-app.yml`); the SDK is the only data access; `.lightdash/context/` holds the project's semantic layer and theme.
+- `developing-data-apps-locally` — the local workflow: edit `src/`, `npm run build`, `lightdash apps preview`, `lightdash upload --apps <slug>`; the SDK is the only data access; `.lightdash/context/` holds the project's semantic layer and theme.
 
 Edit only `src/`. Root config files are read-only reference — the server rebuilds against a trusted template.
 
-The local `npm install && npm run build` is an optional pre-check. 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 create app` 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.
 
 Build with the template's preinstalled dependency set (see `package.json`). Adding new npm packages only works when the instance 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

@@ -1,12 +1,12 @@
 # {{APP_NAME}} — Lightdash data app (local copy)
 
-Downloaded with the Lightdash CLI (`lightdash download`).
+Created or downloaded with the Lightdash CLI.
 
 ## Edit → build → upload
 1. Edit files under `src/`.
-2. Optionally, `npm install && npm run build` to check it compiles locally. If install fails in your environment, skip it — 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 create app` 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.
 3. Optionally, preview against real data: `lightdash apps preview` (needs a successful `npm install`).
-4. `lightdash upload --apps` — Lightdash rebuilds and serves the app.
+4. `lightdash upload --apps <slug>` (the `slug` from `lightdash-app.yml`) — Lightdash rebuilds and serves the app.
 
 Local preview uses your existing CLI login through a project- and route-restricted loopback proxy; the credential is not written into this folder or exposed to browser code. It runs local tooling as your OS user (with access to that user's files, including the existing CLI config) and shows data under your own permissions, so preview only source/dependencies you trust. Host-mediated features such as external connections and data-app-viz context still need testing after upload.
 

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

@@ -1,11 +1,11 @@
 ---
 name: developing-data-apps-locally
-description: Use when editing a downloaded Lightdash data app on your machine — how local editing, building, and re-uploading work, and what is read-only.
+description: Use when editing a locally created or downloaded Lightdash data app — how local editing, building, and uploading work, and what is read-only.
 ---
 
 # Developing Lightdash Data Apps Locally
 
-You are editing a Lightdash **data app** that was downloaded with the Lightdash CLI (`lightdash download`).
+You are editing a Lightdash **data app** that was created or downloaded with the Lightdash CLI.
 
 ## The only way to reach data is the SDK
 
@@ -28,8 +28,8 @@ You are editing a Lightdash **data app** that was downloaded with the Lightdash
 ## The edit → build → upload loop
 
 1. Edit files under `src/` only.
-2. Optionally, `npm install` then `npm run build` to check it compiles. This is an **optional local pre-check** — see below.
-3. `lightdash upload --apps <appUuid>` (the `appUuid` from this folder's `lightdash-app.yml`) — the **server** rebuilds and serves the app. The server rebuild, not your local build, is what ships.
+2. Optionally, run `npm run build` to check it compiles. Apps made with `lightdash create app` already have their initial dependencies installed. After `lightdash download`, if you choose to do the local pre-check and `node_modules` is absent, run `npm install` first. This is an **optional local pre-check** — see below.
+3. `lightdash upload --apps <slug>` (the `slug` from this folder's `lightdash-app.yml`) — the **server** rebuilds and serves the app. The server rebuild, not your local build, is what ships.
 
 ## The local build is optional — never fight a failing install
 
@@ -37,7 +37,7 @@ You are editing a Lightdash **data app** that was downloaded with the Lightdash
 - 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 on instances 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.
-- **Never run dependency lifecycle scripts.** The app's `.npmrc` sets `ignore-scripts=true` — leave it. A downloaded app can be authored by someone else, and their dependencies' install scripts must not execute on this machine. Explicit commands such as `npm run build` still work.
+- **Never run dependency lifecycle scripts.** The app's `.npmrc` sets `ignore-scripts=true` — leave it. A downloaded app can be authored by someone else, and their dependencies' install scripts must not execute on this machine. Explicit `npm run build`/`npm run dev` and `pnpm build`/`pnpm dev` commands still work.
 
 ## Preview locally against real data
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.49.0",
+  "version": "1.50.1",
   "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.49.0",
-    "@lightdash/warehouses": "1.49.0"
+    "@lightdash/common": "1.50.1",
+    "@lightdash/warehouses": "1.50.1"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",