@prisma/composer 0.28.0-dev.2 → 0.28.0-dev.3

package/dist/node.d.mts

@@ -6,9 +6,19 @@ import "./index-DeocL1di.mjs";
 interface NodeBuildAdapter extends BuildAdapter {
   readonly type: 'node';
   readonly dir?: string;
+  /** Whether the build inlined its packages (`'bundled'`, the default) or left them for deploy to stage from `node_modules` (`'external'`). */
+  readonly dependencies?: NodeDependencies;
 }
+/**
+ * How the build treats installed packages, in bundler terms (esbuild's and
+ * Rollup's `external`, Vite's `ssr.external`). `'bundled'`: the build inlined
+ * them, so deploy copies exactly what was built. `'external'`: the build left
+ * them as imports, so deploy traces `entry` and stages the installed packages
+ * it imports.
+ */
+type NodeDependencies = 'bundled' | 'external';
 /** The two forms an author may write. `dir?: never` on the single-file branch is what makes them exclusive: with `dir`, `entry` is required and names a file inside it. */
-type NodeBuildOptions = {
+type NodeBuildOptions = ({
   module: string;
   entry: string;
   dir?: never;
@@ -16,6 +26,9 @@ type NodeBuildOptions = {
   module: string;
   dir: string;
   entry: string;
+}) & {
+  /** `'bundled'` (default) ships exactly what was built. `'external'` also stages the installed packages `entry` imports. */
+  dependencies?: NodeDependencies;
 };
 declare const nodeBuild: (opts: NodeBuildOptions) => NodeBuildAdapter;
 //#endregion

package/dist/node.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"node.d.mts","names":[],"sources":["../../../0-framework/2-authoring/node/dist/index.d.mts"],"mappings":";;;;;UAGU,yBAAyB;WACxB;WACA;;;KAGN;EACH;EACA;EACA;;EAEA;EACA;EACA;;cAEY,YAAY,MAAM,qBAAqB"}
+{"version":3,"file":"node.d.mts","names":[],"sources":["../../../0-framework/2-authoring/node/dist/index.d.mts"],"mappings":";;;;;UAGU,yBAAyB;WACxB;WACA;;WAEA,eAAe;;;;;;;;;KASrB;;KAEA;EACH;EACA;EACA;;EAEA;EACA;EACA;;;EAGA,eAAe;;cAEH,YAAY,MAAM,qBAAqB"}

package/dist/node.mjs

@@ -4,7 +4,8 @@ const nodeBuild = (opts) => ({
 	type: "node",
 	module: opts.module,
 	entry: opts.entry,
-	...opts.dir === void 0 ? {} : { dir: opts.dir }
+	...opts.dir === void 0 ? {} : { dir: opts.dir },
+	...opts.dependencies === void 0 ? {} : { dependencies: opts.dependencies }
 });
 //#endregion
 export { nodeBuild as default };

package/dist/node.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"node.mjs","names":[],"sources":["../../../0-framework/2-authoring/node/dist/index.mjs"],"sourcesContent":["//#region src/node.ts\nconst nodeBuild = (opts) => ({\n\textension: \"@prisma/composer/node\",\n\ttype: \"node\",\n\tmodule: opts.module,\n\tentry: opts.entry,\n\t...opts.dir === void 0 ? {} : { dir: opts.dir }\n});\n//#endregion\nexport { nodeBuild as default };\n\n//# sourceMappingURL=index.mjs.map"],"mappings":";AACA,MAAM,aAAa,UAAU;CAC5B,WAAW;CACX,MAAM;CACN,QAAQ,KAAK;CACb,OAAO,KAAK;CACZ,GAAG,KAAK,QAAQ,KAAK,IAAI,CAAC,IAAI,EAAE,KAAK,KAAK,IAAI;AAC/C"}
+{"version":3,"file":"node.mjs","names":[],"sources":["../../../0-framework/2-authoring/node/dist/index.mjs"],"sourcesContent":["//#region src/node.ts\nconst nodeBuild = (opts) => ({\n\textension: \"@prisma/composer/node\",\n\ttype: \"node\",\n\tmodule: opts.module,\n\tentry: opts.entry,\n\t...opts.dir === void 0 ? {} : { dir: opts.dir },\n\t...opts.dependencies === void 0 ? {} : { dependencies: opts.dependencies }\n});\n//#endregion\nexport { nodeBuild as default };\n\n//# sourceMappingURL=index.mjs.map"],"mappings":";AACA,MAAM,aAAa,UAAU;CAC5B,WAAW;CACX,MAAM;CACN,QAAQ,KAAK;CACb,OAAO,KAAK;CACZ,GAAG,KAAK,QAAQ,KAAK,IAAI,CAAC,IAAI,EAAE,KAAK,KAAK,IAAI;CAC9C,GAAG,KAAK,iBAAiB,KAAK,IAAI,CAAC,IAAI,EAAE,cAAc,KAAK,aAAa;AAC1E"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/composer",
-  "version": "0.28.0-dev.2",
+  "version": "0.28.0-dev.3",
   "type": "module",
   "description": "Prisma Composer — build a Prisma App by composing Modules. Core authoring, deploy pipeline, and the service-rpc/node/nextjs authoring surfaces. The command family the `prisma` CLI mounts lives in @prisma/composer-cli.",
   "exports": {
@@ -39,15 +39,15 @@
     "@prisma/management-api-sdk": "^1.80.0"
   },
   "devDependencies": {
-    "@internal/assemble": "0.28.0-dev.2",
-    "@internal/cli": "0.28.0-dev.2",
-    "@internal/core": "0.28.0-dev.2",
-    "@internal/foundation": "0.28.0-dev.2",
-    "@internal/lowering": "0.28.0-dev.2",
-    "@internal/nextjs": "0.28.0-dev.2",
-    "@internal/node": "0.28.0-dev.2",
-    "@internal/service-rpc": "0.28.0-dev.2",
-    "@internal/tsdown-config": "0.28.0-dev.2",
+    "@internal/assemble": "0.28.0-dev.3",
+    "@internal/cli": "0.28.0-dev.3",
+    "@internal/core": "0.28.0-dev.3",
+    "@internal/foundation": "0.28.0-dev.3",
+    "@internal/lowering": "0.28.0-dev.3",
+    "@internal/nextjs": "0.28.0-dev.3",
+    "@internal/node": "0.28.0-dev.3",
+    "@internal/service-rpc": "0.28.0-dev.3",
+    "@internal/tsdown-config": "0.28.0-dev.3",
     "@types/node": "^26.0.1",
     "tsdown": "^0.22.7",
     "typescript": "^6.0.3"

package/skills/prisma-composer-core-concepts/SKILL.md

@@ -2,7 +2,7 @@
 name: prisma-composer-core-concepts
 metadata:
   library: "@prisma/composer"
-  library_version: "0.28.0-dev.2"
+  library_version: "0.28.0-dev.3"
   version: 2026.9.1
 description: >-
   Use when deploying or managing an app that uses Prisma Composer
@@ -195,11 +195,12 @@ be reimplemented:
 
 ## Builds are yours
 
-You build, the framework assembles. For a plain server process, `entry` must
-point at a single self-contained ESM file: everything inlined except runtime
-built-ins (`bun`, `bun:*`, `node:*`). Deploy copies that one file and never
-ships `node_modules`, so anything left un-inlined fails at boot, not at
-deploy. Rules that bite:
+You build, the framework assembles. For a plain server process, `entry`
+points at the ESM file your build produced. By default
+(`dependencies: 'bundled'`) deploy copies exactly that and never ships
+`node_modules`, so everything except runtime built-ins (`bun`, `bun:*`,
+`node:*`) must be inlined, or it fails at boot, not at deploy. Rules that
+bite:
 
 1. **Two services in one package means two separate builds**, one per entry.
    A single multi-entry build splits shared code into a chunk neither output
@@ -209,12 +210,19 @@ deploy. Rules that bite:
    copied verbatim, so the server must resolve siblings against
    `import.meta.url`, not the working directory. The tree must contain no
    symlinks: the packager rejects them, names the link, and assembly fails.
-3. **Next.js**: `next build` with `output: 'standalone'` is the whole build;
+3. **A build that leaves packages external sets `dependencies: 'external'`**
+   (either form). Deploy then traces `entry` and stages the installed
+   packages it imports, which can take minutes on a large build. Astro's Node
+   adapter, SvelteKit's `adapter-node` and React Router's server build leave
+   packages external by default. The default, `'bundled'`, copies exactly
+   what was built. A service that fails to start with
+   `Cannot find package 'x'` needs `x` bundled, or `dependencies: 'external'`.
+4. **Next.js**: `next build` with `output: 'standalone'` is the whole build;
    `nextjs({ module, appDir })` names the app root. Any page or action that
    calls `load()` needs `export const dynamic = 'force-dynamic'`, because
    the runtime environment doesn't exist at build time and Next ignores
    runtime env for prerendered routes.
-4. **Always build before `deploy` or `dev`.** Neither builds for you.
+5. **Always build before `deploy` or `dev`.** Neither builds for you.
 
 Deploy configuration is the `composer` section of `prisma.config.ts`, and
 nothing else. It registers extensions (`prismaCloud()`, `nodeBuild()`,
@@ -310,9 +318,9 @@ its duration (`✔ assemble web (3m 42s)`), and ends with the real total
 (`Deployed <app> to <stage> in 5m 25s.`). Steps: load config and app, one
 assemble per service, connect to project and branch, check environment
 variables, plan and apply (one step: alchemy does both in one process), record
-result. A slow assemble is usually a Node service with `dir` set, whose
-runtime dependencies are being traced. In json mode (`--json`, or stdout not
-a terminal) each step is a `step-started`/`step-finished` line whose `data`
+result. A slow assemble is usually a Node service with
+`dependencies: 'external'`, whose runtime dependencies are being traced. In json mode (`--json`, or stdout not a
+terminal) each step is a `step-started`/`step-finished` line whose `data`
 holds `durationMs` plus whatever the build adapter or deploy target reported;
 those extra fields vary, so don't parse them as a stable format. The
 `deploy` operation's `onEvent` receives the same steps, and its result's