Merge pull request #63 from prisma/feat/config-app-config-file

feat(config): introduce app config file

Author: luanvdw

docs/product/command-spec.md

@@ -58,7 +58,7 @@ Out of scope for the current beta:
   non-TTY stderr, and when `NO_UPDATE_NOTIFIER` is set. When shown, update
   notifications are stderr-only human output and do not change the original
   command result.
-- Public Beta does not read or write committed config files such as `prisma.config.ts` or `.prisma/settings.json` for Project -> Branch -> App resolution. `.prisma/local.json` is a gitignored local pin/cache, not a declarative repo config file.
+- Public Beta does not read or write committed config files such as `prisma.config.ts` or `.prisma/settings.json` for Project -> Branch -> App resolution. `.prisma/local.json` is a gitignored local pin/cache, not a declarative repo config file. `prisma.app.json` is only for app build settings.
 - Remote commands do not silently change local context.
 
 ## Authentication
@@ -627,6 +627,11 @@ Behavior:
 - writes `.prisma/local.json` after Project binding succeeds and before build/deploy starts, so retries after a failed deploy do not repeat setup
 - before asking `Customize build settings? (y/N)`, previews the detected framework and runtime so the user can see the defaults they are accepting or changing
 - asks `Customize build settings? (y/N)` only while binding the directory for the first time, and only asks for Framework and HTTP port when the user opts in
+- for Next.js, TanStack Start, and Bun/Hono deploys, reads or creates `prisma.app.json` before build and uses it for app build settings:
+  - `Build Command` prefers `<package-manager> run build` when `package.json` has `scripts.build`
+  - otherwise `Build Command` falls back to the framework default, such as `next build`
+  - `Output Directory` is a literal framework output path, such as `.next/standalone`, `.output`, or `.`
+- does not overwrite an existing `prisma.app.json`; edit the file or delete it and rerun deploy to regenerate defaults
 - after setup, deploy prints `Deploying to <Project> / <Branch> / <App>`; later deploys print a compact target header such as `Deploying ./j1 to j1 / main / j1`
 - deploy progress uses short stage copy (`Building locally...`, `Built <size>`, `Uploading...`, `Uploaded`, `Deploying...`, `Deployed`) and never prints `Status: running` or `Deployment is running at ...`
 - success human output prints `Live in <duration>`, the URL on its own line, and `Logs   prisma-cli app logs`
@@ -647,11 +652,12 @@ Behavior:
 - if schema setup fails, deploy stops before the app build/deploy starts
 - `--env DATABASE_URL=...`, `--env DIRECT_URL=...`, or the same keys loaded from an env file suppress automatic database prompting; combining those database env vars with `--db` is rejected
 - maps user-facing framework names to deploy build strategies
+- does not accept `--build-command` or `--output-directory`; custom build settings are edited in `prisma.app.json`, which is initially generated from `package.json` `scripts.build` and framework defaults for config-backed deploy types
 - uses `src/index.ts` as the Hono deploy entrypoint when the app has no `package.json#main` or `package.json#module` and that file exists
 - supports vanilla Bun apps with `--framework bun` using `package.json#main` or `package.json#module`, or with `--entry <path>`
 - treats `--entry <path>` without `--framework` as a Bun app deploy
 - does not print secret values
-- returns app, deployment id, URL, and next steps in `--json` output
+- returns app, deployment id, URL, deploy settings including `prisma.app.json` status/build/output metadata, and next steps in `--json` output
 
 Examples:
 

docs/product/error-conventions.md

@@ -169,6 +169,7 @@ These codes are the minimum stable set for the MVP:
 - `LOCAL_PROJECT_WORKSPACE_MISMATCH`
 - `LOCAL_STATE_STALE`
 - `BRANCH_NOT_DEPLOYABLE`
+- `APP_CONFIG_INVALID`
 - `FRAMEWORK_NOT_DETECTED`
 - `DEPLOYMENT_NOT_FOUND`
 - `NO_DEPLOYMENTS`
@@ -214,6 +215,7 @@ Recommended meanings:
 - `LOCAL_PROJECT_WORKSPACE_MISMATCH`: local Project pin points at a different workspace than the active authenticated workspace; callers should sign in to the linked workspace or relink the directory
 - `LOCAL_STATE_STALE`: local Project pin no longer matches platform data and continuing would be ambiguous
 - `BRANCH_NOT_DEPLOYABLE`: command tried to deploy to a non-deployable branch context
+- `APP_CONFIG_INVALID`: `prisma.app.json` is missing required build settings, has invalid JSON, or points outside the app root
 - `FRAMEWORK_NOT_DETECTED`: app deploy could not detect a supported Beta framework and no explicit framework/build type was provided
 - `DEPLOYMENT_NOT_FOUND`: requested deployment id does not exist
 - `NO_DEPLOYMENTS`: command resolved a branch or app but found no deployments

docs/product/output-conventions.md

@@ -314,6 +314,7 @@ Examples:
 - `app deploy` should state the resolved target that matters in the current slice
 - first local `app deploy` binding should make the Project choice explicit before work begins
 - subsequent `app deploy` calls should use a compact target header such as `Deploying ./j1 to j1 / main / j1`
+- config-backed `app deploy` builds should show whether they created or used `prisma.app.json` before build starts: `Build Command` with its source when inferred, and `Output Directory` as a literal path such as `.next/standalone` rather than an opaque framework default label
 - `app logs` should state the deployment it resolved
 - `app list-deploys` should state which app or branch is being listed
 

docs/product/resource-model.md

@@ -38,6 +38,7 @@ Rules:
 - `project` is not the same thing as `app`
 - Public Beta does not read or write committed config files such as `prisma.config.ts` or `.prisma/settings.json` for project resolution
 - `.prisma/local.json` is a gitignored local pin/cache for Workspace and Project IDs; it is not a declarative repo config file
+- `prisma.app.json` is a committed app build-settings file only; it must not contain Workspace, Project, Branch, App, env, or secret resolution state
 - Project setup is explicit: users choose an existing Project or explicitly create a new one before remote work starts
 - `app deploy` may orchestrate Project setup, but it must not silently choose or create Project scope
 - everything under a project happens in a branch
@@ -103,6 +104,7 @@ Rules:
 - the runtime app service is scoped by branch in the platform model
 - the app may be selected or created as part of app deployment workflows
 - app selection is local CLI state when needed for the beta package
+- app build settings may live in `prisma.app.json` beside `package.json`; v1 fields are `buildCommand` and `outputDirectory`
 
 ### Deployment
 

packages/cli/src/controllers/app.ts

@@ -76,6 +76,9 @@ import {
   executePreviewBuild,
   PREVIEW_BUILD_TYPES,
   RESOLVED_PREVIEW_BUILD_TYPES,
+  resolveOrCreatePreviewBuildSettings,
+  type PreviewBuildSettingsBuildType,
+  type PreviewBuildSettingsResolution,
   type ResolvedPreviewBuildType,
   type PreviewBuildType,
 } from "../lib/app/preview-build";
@@ -322,6 +325,12 @@ export async function runAppDeploy(
   const buildType = framework.buildType;
   assertSupportedEntrypoint(buildType, options?.entrypoint, "deploy");
   const entrypoint = await resolveDeployEntrypoint(context.runtime.cwd, framework, options?.entrypoint, context.runtime.signal);
+  const buildSettingsResolution = await resolveOrCreatePreviewBuildSettings({
+    appPath: context.runtime.cwd,
+    buildType,
+    signal: context.runtime.signal,
+  });
+  maybeRenderDeployBuildSettings(context, buildSettingsResolution);
   const portMapping = parseDeployPortMapping(String(runtime.port));
   const branchDatabaseSetup = await maybeSetupBranchDatabase(context, provider, projectId, toBranchDatabaseDeployBranch(target.branch), {
     db: options?.db,
@@ -339,6 +348,7 @@ export async function runAppDeploy(
     region: selectedApp.region,
     entrypoint,
     buildType,
+    buildSettings: buildSettingsResolution.settings,
     portMapping,
     envVars,
     interaction: undefined,
@@ -369,6 +379,18 @@ export async function runAppDeploy(
       },
       deployment: deployResult.deployment,
       deploySettings: {
+        config: {
+          path: buildSettingsResolution.relativeConfigPath,
+          status: buildSettingsResolution.status,
+        },
+        buildCommand: {
+          value: buildSettingsResolution.settings.buildCommand,
+          source: buildSettingsResolution.settings.buildCommandSource,
+        },
+        outputDirectory: {
+          value: buildSettingsResolution.settings.outputDirectory,
+          source: buildSettingsResolution.settings.outputDirectorySource,
+        },
         framework: {
           key: framework.key,
           buildType,
@@ -2598,7 +2620,7 @@ async function resolveDeployBranch(context: CommandContext, explicitBranchName:
 
 interface ResolvedDeployFramework {
   key: string;
-  buildType: ResolvedPreviewBuildType;
+  buildType: PreviewBuildSettingsBuildType;
   displayName: string;
   annotation: string;
 }
@@ -2743,7 +2765,6 @@ async function detectNextConfig(cwd: string, signal: AbortSignal): Promise<{ exi
   const candidates = [
     "next.config.js",
     "next.config.mjs",
-    "next.config.cjs",
     "next.config.ts",
     "next.config.mts",
   ];
@@ -2869,6 +2890,36 @@ async function maybeRenderDeploySetupBlock(
   context.output.stderr.write(`${prefix} ${details.projectName} / ${details.branchName} / ${details.appName}\n\n`);
 }
 
+function maybeRenderDeployBuildSettings(
+  context: CommandContext,
+  resolution: PreviewBuildSettingsResolution,
+): void {
+  if (context.flags.json || context.flags.quiet) {
+    return;
+  }
+
+  const settings = resolution.settings;
+  const title = resolution.status === "created"
+    ? `Created ${resolution.relativeConfigPath}`
+    : `Using ${resolution.relativeConfigPath}`;
+
+  context.output.stderr.write(
+    `${title}\n`
+      + `${renderDeployOutputRows(context.ui, [
+        {
+          label: "Build Command",
+          value: settings.buildCommand ?? "none",
+          origin: settings.buildCommandSource ?? undefined,
+        },
+        {
+          label: "Output Directory",
+          value: settings.outputDirectory,
+          origin: settings.outputDirectorySource ?? undefined,
+        },
+      ]).join("\n")}\n\n`,
+  );
+}
+
 function maybeRenderProjectLinked(
   context: CommandContext,
   directory: string,

packages/cli/src/lib/app/bun-project.ts

@@ -4,6 +4,7 @@ import path from "node:path";
 export interface BunPackageJsonLike {
   main?: unknown;
   module?: unknown;
+  packageManager?: unknown;
   scripts?: unknown;
   dependencies?: unknown;
   devDependencies?: unknown;