feat: enable Prisma Compute deploys for the NestJS template (#46)

* feat: enable Prisma Compute deploys for the NestJS template

Compute's SDK gained a NestJS build strategy (project-compute #94), so the
nest template can now deploy. Add it to COMPUTE_DEPLOYABLE_TEMPLATES and ship
a prisma.compute.ts with framework "nestjs" (detected, no entrypoint; the
default HTTP port 3000 matches the template's listen port).

The compute:deploy script and README Compute sections wire up automatically
off the deployable gate.

* fix: actually deploy the NestJS template, add its compute-sdk dep

Enabling nest needs three registries, not one. The first PR only added it to
COMPUTE_DEPLOYABLE_TEMPLATES (which gates the deploy prompt), so the prompt
showed but the deploy was skipped:

- DEPLOY_OPTIONS_BY_TEMPLATE gates the actual deploy. Without a nest entry,
  collectComputeDeployContext returned null after the user confirmed, so no
  deploy ran and no URL was printed.
- computeConfigTemplates adds @prisma/compute-sdk as a devDependency for the
  generated prisma.compute.ts types.

nest is a single-app template, so its deploy entry is {} (no configTarget).

* docs: list nest as a Compute-deployable template in the README

* fix: nest build must emit compiled output for deploy (bun/node)

The NestJS deploy strategy compiles and ships dist/, so its build script must
emit. The shared runtimeScript helper used `tsc --noEmit` for bun (and
`deno check` for deno) because those runtimes execute TypeScript directly —
fine for hono/elysia (the SDK bundles their source) but it left nest with no
dist/main.js, so deploys failed with "Build failed locally" under bun.

Add an `emit` option to runtimeScript; nest opts in so its build compiles to
dist on every node-style PM and bun. Deno keeps `deno check` — the Deno nest
variant uses Deno APIs and isn't built for the node-based Compute runtime.

Author: AmanVarshney01

README.md

@@ -101,6 +101,7 @@ Prisma Compute deployment is currently supported for:
 
 - `hono`
 - `elysia`
+- `nest`
 - `next`
 - `astro`
 - `nuxt`
@@ -152,7 +153,7 @@ When Prisma Compute deploy is selected, the skills add-on recommends the `prisma
 
 ## Deploy to Prisma Compute
 
-After scaffolding, `create-prisma` can deploy your app to [Prisma Compute](https://www.prisma.io/docs/compute), the serverless hosting for TypeScript apps that runs next to your Prisma Postgres database. It is offered for the templates the Prisma CLI can deploy today: `hono`, `elysia`, `next`, `astro`, `nuxt`, `tanstack-start`, and `turborepo`.
+After scaffolding, `create-prisma` can deploy your app to [Prisma Compute](https://www.prisma.io/docs/compute), the serverless hosting for TypeScript apps that runs next to your Prisma Postgres database. It is offered for the templates the Prisma CLI can deploy today: `hono`, `elysia`, `nest`, `next`, `astro`, `nuxt`, `tanstack-start`, and `turborepo`.
 
 Accept the deploy prompt when it appears, or pass the flag:
 

src/constants/dependencies.ts

@@ -28,6 +28,7 @@ export type CreateTemplateDependencyTarget = {
 const computeConfigTemplates = new Set<CreateTemplate>([
   "hono",
   "elysia",
+  "nest",
   "next",
   "astro",
   "nuxt",

src/tasks/deploy-to-compute.ts

@@ -21,6 +21,7 @@ const DEPLOY_OPTIONS_BY_TEMPLATE: Partial<
 > = {
   hono: {},
   elysia: {},
+  nest: {},
   next: {},
   astro: {},
   nuxt: {},

src/templates/shared.ts

@@ -102,6 +102,7 @@ Handlebars.registerHelper(
       sourceEntrypoint,
       builtEntrypoint,
       denoFlags: getOptionalHashStringList(hash, "denoFlags"),
+      emit: hash.emit === true,
     });
   },
 );

src/types.ts

@@ -101,6 +101,7 @@ export const CreateScaffoldOptionsSchema = z.object({
 export const COMPUTE_DEPLOYABLE_TEMPLATES: ReadonlySet<CreateTemplate> = new Set<CreateTemplate>([
   "hono",
   "elysia",
+  "nest",
   "next",
   "astro",
   "nuxt",

src/utils/package-manager.ts

@@ -14,6 +14,10 @@ type RuntimeScriptOptions = {
   sourceEntrypoint: string;
   builtEntrypoint?: string;
   denoFlags?: string[];
+  // When true, `build` compiles to `dist` instead of only type-checking.
+  // Templates that deploy a compiled artifact (e.g. NestJS) need this; bun and
+  // deno otherwise run TypeScript directly and skip emit.
+  emit?: boolean;
 };
 
 const packageManagerManifestValues = {
@@ -198,7 +202,7 @@ export function getRuntimeScriptCommand(
   kind: RuntimeScriptKind,
   options: RuntimeScriptOptions,
 ): string {
-  const { sourceEntrypoint, builtEntrypoint, denoFlags = [] } = options;
+  const { sourceEntrypoint, builtEntrypoint, denoFlags = [], emit = false } = options;
 
   if (packageManager === "deno") {
     switch (kind) {
@@ -213,6 +217,9 @@ export function getRuntimeScriptCommand(
           sourceEntrypoint,
         ]);
       case "build":
+        // Deno runs TypeScript directly; there is no node-style compiled
+        // artifact to emit here (the Deno nest variant uses Deno APIs and is
+        // not built for the node-based Compute runtime).
         return `deno check ${sourceEntrypoint}`;
       case "start":
         return joinCommandParts([
@@ -231,7 +238,7 @@ export function getRuntimeScriptCommand(
       case "dev":
         return `bun --watch ${sourceEntrypoint}`;
       case "build":
-        return "tsc --noEmit";
+        return emit ? "tsc" : "tsc --noEmit";
       case "start":
         return `bun ${sourceEntrypoint}`;
     }

templates/create/nest/package.json.hbs

@@ -7,7 +7,7 @@
   "type": "module",
   "scripts": {
     "dev": "{{runtimeScript packageManager "dev" "src/main.ts" "dist/main.js"}}",
-    "build": "{{runtimeScript packageManager "build" "src/main.ts" "dist/main.js"}}",
+    "build": "{{runtimeScript packageManager "build" "src/main.ts" "dist/main.js" emit=true}}",
     "start": "{{runtimeScript packageManager "start" "src/main.ts" "dist/main.js"}}"
   },
   "dependencies": {

templates/create/nest/prisma.compute.ts.hbs

@@ -0,0 +1,9 @@
+import { defineComputeConfig } from "@prisma/compute-sdk/config";
+
+export default defineComputeConfig({
+  app: {
+    name: "{{projectName}}",
+    framework: "nestjs",
+    env: ".env",
+  },
+});