Skip to content

Feat: add Nestjs backend integration - #1119

Open
modejota wants to merge 7 commits into
AmanVarshney01:mainfrom
modejota:feat/nestjs-backend-integration
Open

modejota wants to merge 7 commits into
AmanVarshney01:mainfrom
modejota:feat/nestjs-backend-integration

Conversation

@modejota

@modejota modejota commented Jul 21, 2026 •

Copy link
Copy Markdown
Contributor

Given the community requesting to add Nest.js as a backend framework in #428 I decided to do it on my own. Hope this helps.

Summary by CodeRabbit

  • New Features
    • Added Nest.js as a server framework option, with support for Bun and Node runtimes, Prisma or Mongoose, and Docker or Vercel deployment.
    • Added generated Nest.js server setups with optional Better Auth, Evlog logging, and a Todo REST example for supported web and native frontends.
  • Bug Fixes
    • Updated configuration guidance and compatibility checks to support Nest.js and identify incompatible selections.

@vercel

vercel Bot commented Jul 21, 2026

Copy link
Copy Markdown

@modejota is attempting to deploy a commit to the Better T Stack Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 21, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e8673045-f135-4e29-9888-141ce04fae7a
📥 Commits

Reviewing files that changed from the base of the PR and between 8f10d91 and b4b6bee.

⛔ Files ignored due to path filters (1)
  • packages/template-generator/src/templates.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (4)
  • apps/cli/test/nest.test.ts
  • packages/template-generator/src/post-process/vercel-config.ts
  • packages/template-generator/templates/backend/server/nest/src/app.controller.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/todos.controller.ts.hbs

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.


Walkthrough

This change adds Nest.js as a supported backend. It updates stack selection and validation, generates Nest.js server and Todo templates, connects web and native clients, and adds Nest.js support to EVLog setup.

Changes

Nest.js backend support

Layer / File(s) Summary
Selection and compatibility rules
packages/types/src/*, apps/cli/src/prompts/*, apps/cli/src/utils/*, apps/web/src/lib/*, apps/cli/test/*, apps/web/test/*
The CLI and web stack builder now offer and validate Nest.js, including its supported runtimes, ORMs, API, auth, payments, deployments, and examples. Compatibility tests cover valid and invalid combinations.
Generator wiring and runtime outputs
packages/template-generator/src/processors/*, packages/template-generator/src/template-handlers/examples.ts, packages/template-generator/src/post-process/vercel-config.ts, packages/template-generator/templates/backend/server/base/*, packages/template-generator/templates/deploy/docker/server/Dockerfile.hbs, packages/template-generator/templates/db/prisma/*/src/index.ts.hbs, apps/cli/test/generated-builds.test.ts
Generation now selects Nest.js dependencies and main.ts entrypoints, updates deployment output and generated README data, and creates Nest-specific Todo templates. Prisma templates also re-export Prisma.
Nest.js server and Todo templates
packages/template-generator/templates/backend/server/nest/*, packages/template-generator/templates/examples/todo/nest/server/*, apps/cli/test/nest.test.ts
The generated server includes bootstrap, health, auth, and Todo module wiring. The Todo API validates inputs and uses Prisma or Mongoose persistence.
Frontend Todo clients
packages/template-generator/templates/examples/todo/nest/*, packages/template-generator/templates/frontend/*, apps/cli/test/nest.test.ts
Generated web and native clients provide health and Todo queries and mutations. Frontend templates include query-client and provider wiring for the Nest.js Todo example.
EVLog Nest.js integration
apps/cli/src/helpers/addons/evlog-setup.ts, apps/cli/test/addons.test.ts
EVLog setup adds logger initialization to the Nest.js entry point and configures EvlogModule, with optional development filesystem draining.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to b4b6b

Nest.js support is consistent with the existing Todo example behavior. Vercel function configuration now targets the Nest entrypoint, and no blocking issues remain.

Security Architecture Review

Security architecture risk: 🟡 Moderate · up to b4b6b

The generated Nest Todo example permits public access to shared Todo data, including writes, even when authentication is selected. This follows the existing examples’ public-data design rather than introducing a demonstrated authorization regression. Exposure is conditional on generating and deploying the example, but authentication and validation behavior still require runtime confirmation.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — For a reachable generated Nest deployment containing the Todo example, the independently attackable data scope is the complete Todo dataset: enumeration exposes record IDs, and each exposed ID can be used for mutation or deletion. This trace does not demonstrate access to credentials, other datasets, generator infrastructure, or other deployments.

Security Findings and Attack Paths

  • observed — The retained, high-severity authorization finding identifies external anonymous Todo access and unscoped database writes. The static path is caller-controlled REST input through the anonymously marked controller into list, create, ID-only update, and ID-only delete operations; validation does not supply authorization.
  • observed — The strongest counterevidence to a newly introduced authorization-design regression is the unchanged baseline: Prisma and Mongoose Todo routers already expose equivalent public reads and writes without owner predicates. The public shared-data condition predates this PR; Nest adds another implementation of it rather than a demonstrated increase in per-deployment authority.

Trust Boundaries and Controls

  • observed — The bootstrap installs a whitelist-and-transform ValidationPipe for Todo generation, imports reflect-metadata, and the Nest TypeScript configuration enables decorator metadata. These establish intended request-shape controls, not identity or ownership controls. The supplied evidence leaves effective dependency guard semantics and generated-runtime validation behavior unresolved; configured CORS is not authorization for direct HTTP callers.

Resilience and Maintainability Implications

  • inferred — The inspected mutations have no intermediate reservation or cleanup state. Repeating an update to the same completed value is effectively idempotent; successful deletion followed by repetition becomes not-found, while repeated creation can add multiple records. Concurrent updates have no explicit version check. These semantics do not reveal a separate security-sensitive partial-transition defect, although ORM-specific interruption and concurrency behavior was not verified at runtime.

Hardening Proposals

  • proposed — If Todo data is intended to be private, require identity and enforce subject-scoped ownership on every read and mutation; removing AllowAnonymous alone would not create record-level isolation. If the shared public demo is intentional, make that contract explicit for generated-project users.
  • proposed — Resolve the remaining control uncertainty by checking anonymous and authenticated CRUD behavior and malformed DTO rejection in generated applications under their development and production build paths.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 3.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 30 functions across 30 files. (2 skipped: … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: adding NestJS as a backend integration.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 3.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 30 functions across 30 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
packages/template-generator/templates/frontend/native/bare/app/_layout.tsx.hbs (1)

139-164: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Generate the Clerk bridge for Nest Todo projects with no API selected.

The widened Nest Todo branches render <ClerkApiAuthBridge />, but its declaration—and, in native/TanStack Router templates, the required Clerk hook imports—remain gated on api !== "none". A Clerk + Nest + Todo + api="none" project therefore fails type-checking.

  • packages/template-generator/templates/frontend/native/bare/app/_layout.tsx.hbs#L139-L164: include Nest Todo in the Clerk hook/bridge guards.
  • packages/template-generator/templates/frontend/native/unistyles/app/_layout.tsx.hbs#L155-L200: include Nest Todo in the Clerk hook/bridge guards.
  • packages/template-generator/templates/frontend/native/uniwind/app/_layout.tsx.hbs#L134-L157: include Nest Todo in the Clerk hook/bridge guards.
  • packages/template-generator/templates/frontend/react/next/src/components/providers.tsx.hbs#L94-L109: include Nest Todo in the useAuth and ClerkApiAuthBridge guards.
  • packages/template-generator/templates/frontend/react/tanstack-router/src/main.tsx.hbs#L58-L75: include Nest Todo in the Clerk hook/bridge guards.
packages/template-generator/templates/frontend/react/react-router/src/root.tsx.hbs (1)

161-217: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Wrap the Clerk + Nest Todo app in QueryClientProvider.

With auth="clerk", backend="nest", examples containing "todo", and api="none", Lines 165-213 take the plain fallback instead of the Nest Todo query branch. Todo query hooks then run without a QueryClientProvider. Apply the Nest Todo predicate to the Clerk auth bridge and ORPC provider branch as well.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5bcbff79-8803-44a3-95a5-2fc2fd369eb1

📥 Commits

Reviewing files that changed from the base of the PR and between 4473a3e and 9584301.

⛔ Files ignored due to path filters (1)
  • packages/template-generator/src/templates.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (63)
  • apps/cli/src/helpers/addons/evlog-setup.ts
  • apps/cli/src/prompts/api.ts
  • apps/cli/src/prompts/auth.ts
  • apps/cli/src/prompts/backend.ts
  • apps/cli/src/prompts/orm.ts
  • apps/cli/src/prompts/package-manager.ts
  • apps/cli/src/prompts/payments.ts
  • apps/cli/src/prompts/server-deploy.ts
  • apps/cli/src/utils/compatibility-rules.ts
  • apps/cli/src/utils/config-validation.ts
  • apps/cli/test/addons.test.ts
  • apps/cli/test/backend-runtime.test.ts
  • apps/cli/test/database-orm.test.ts
  • apps/cli/test/deployment.test.ts
  • apps/cli/test/generated-builds.test.ts
  • apps/cli/test/nest.test.ts
  • apps/web/src/app/(home)/new/_components/utils.ts
  • apps/web/src/app/layout.tsx
  • apps/web/src/lib/constant.ts
  • apps/web/test/stack-builder-compatibility.test.ts
  • packages/template-generator/src/post-process/vercel-config.ts
  • packages/template-generator/src/processors/backend-deps.ts
  • packages/template-generator/src/processors/examples-deps.ts
  • packages/template-generator/src/processors/readme-generator.ts
  • packages/template-generator/src/processors/runtime-deps.ts
  • packages/template-generator/src/template-handlers/examples.ts
  • packages/template-generator/src/utils/add-deps.ts
  • packages/template-generator/src/utils/generated-ignore-patterns.ts
  • packages/template-generator/templates/backend/server/base/package.json.hbs
  • packages/template-generator/templates/backend/server/base/tsconfig.json.hbs
  • packages/template-generator/templates/backend/server/base/tsdown.config.ts.hbs
  • packages/template-generator/templates/backend/server/nest/src/app.controller.ts.hbs
  • packages/template-generator/templates/backend/server/nest/src/app.module.ts.hbs
  • packages/template-generator/templates/backend/server/nest/src/app.service.ts.hbs
  • packages/template-generator/templates/backend/server/nest/src/main.ts.hbs
  • packages/template-generator/templates/db/prisma/mongodb/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/mysql/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/postgres/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/sqlite/src/index.ts.hbs
  • packages/template-generator/templates/deploy/docker/server/Dockerfile.hbs
  • packages/template-generator/templates/examples/todo/nest/native/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/dto/create-todo.dto.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/dto/update-todo.dto.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/entities/todo.entity.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/todos.controller.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/todos.module.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/todos.service.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/astro/src/lib/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/nuxt/app/plugins/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/nuxt/app/plugins/vue-query.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/react/src/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/solid/src/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/svelte/src/lib/orpc.ts.hbs
  • packages/template-generator/templates/frontend/native/bare/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/native/unistyles/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/native/uniwind/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/react/next/src/components/providers.tsx.hbs
  • packages/template-generator/templates/frontend/react/react-router/src/root.tsx.hbs
  • packages/template-generator/templates/frontend/react/tanstack-router/src/main.tsx.hbs
  • packages/template-generator/templates/frontend/react/tanstack-start/src/router.tsx.hbs
  • packages/template-generator/templates/frontend/solid/src/main.tsx.hbs
  • packages/template-generator/templates/frontend/svelte/src/routes/+layout.svelte.hbs
  • packages/types/src/schemas.ts

Comment thread apps/cli/src/prompts/package-manager.ts Resolved
@modejota
modejota force-pushed the feat/nestjs-backend-integration branch from cce3a57 to 899d6e4 Compare July 26, 2026 21:34

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2


ℹ️ Review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e57d7958-6b9f-4f5a-831e-c85e9a3f14c9
📥 Commits

Reviewing files that changed from the base of the PR and between 899d6e4 and 8f10d91.

⛔ Files ignored due to path filters (1)
  • packages/template-generator/src/templates.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (49)
  • apps/cli/src/helpers/addons/evlog-setup.ts
  • apps/cli/src/prompts/auth.ts
  • apps/cli/src/prompts/backend.ts
  • apps/cli/src/prompts/orm.ts
  • apps/cli/src/prompts/server-deploy.ts
  • apps/cli/src/utils/compatibility-rules.ts
  • apps/cli/src/utils/config-validation.ts
  • apps/cli/test/addons.test.ts
  • apps/cli/test/backend-runtime.test.ts
  • apps/cli/test/database-orm.test.ts
  • apps/cli/test/deployment.test.ts
  • apps/cli/test/generated-builds.test.ts
  • apps/cli/test/nest.test.ts
  • apps/web/src/app/layout.tsx
  • apps/web/src/lib/constant.ts
  • apps/web/src/lib/stack-validation.ts
  • apps/web/test/stack-builder-compatibility.test.ts
  • packages/template-generator/src/post-process/vercel-config.ts
  • packages/template-generator/src/processors/examples-deps.ts
  • packages/template-generator/src/processors/readme-generator.ts
  • packages/template-generator/src/processors/runtime-deps.ts
  • packages/template-generator/src/processors/varlock.ts
  • packages/template-generator/src/utils/add-deps.ts
  • packages/template-generator/src/utils/generated-ignore-patterns.ts
  • packages/template-generator/templates/backend/server/base/package.json.hbs
  • packages/template-generator/templates/backend/server/base/tsconfig.json.hbs
  • packages/template-generator/templates/backend/server/base/tsdown.config.ts.hbs
  • packages/template-generator/templates/backend/server/nest/src/main.ts.hbs
  • packages/template-generator/templates/db/prisma/mongodb/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/mysql/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/postgres/src/index.ts.hbs
  • packages/template-generator/templates/db/prisma/sqlite/src/index.ts.hbs
  • packages/template-generator/templates/deploy/docker/server/Dockerfile.hbs
  • packages/template-generator/templates/examples/todo/nest/native/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/server/src/todos/todos.service.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/astro/src/lib/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/react/src/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/solid/src/utils/orpc.ts.hbs
  • packages/template-generator/templates/examples/todo/nest/web/svelte/src/lib/orpc.ts.hbs
  • packages/template-generator/templates/frontend/native/bare/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/native/unistyles/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/native/uniwind/app/_layout.tsx.hbs
  • packages/template-generator/templates/frontend/react/next/src/components/providers.tsx.hbs
  • packages/template-generator/templates/frontend/react/react-router/src/root.tsx.hbs
  • packages/template-generator/templates/frontend/react/tanstack-router/src/main.tsx.hbs
  • packages/template-generator/templates/frontend/react/tanstack-start/src/router.tsx.hbs
  • packages/template-generator/templates/frontend/solid/src/App.tsx.hbs
  • packages/types/src/compatibility.ts
  • packages/types/src/schemas.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/web/src/app/layout.tsx

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

Comment on lines +75 to +76
framework: backend === "nest" ? "nestjs" : backend,
entrypoint: backend === "nest" ? "src/main.ts" : "src/index.ts",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

Align Nest Todo routes with the Vercel /api rewrite.

When web and Nest services deploy together, this configuration sets the web server URL to /api and forwards /api/* to Nest. Vercel preserves that request path. The supplied Nest bootstrap sets no global prefix, while the Todo controller uses @Controller("todos"). A client request to /api/todos therefore reaches Nest as /api/todos, not /todos, and misses the Todo route. Add the prefix in Nest or rewrite the path before forwarding it. (vercel.com)

framework: backend,
entrypoint: "src/index.ts",
framework: backend === "nest" ? "nestjs" : backend,
entrypoint: backend === "nest" ? "src/main.ts" : "src/index.ts",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

🔎 Supported by static analysis

🏁 Script executed:

git diff --unified=12 773516e3260fcada2affab2089687bed6834dacc 8f10d91480ccb0a6230ce5a0ced270416bc03064 -- packages/template-generator/src/post-process/vercel-config.ts
printf '\n--- current source ---\n'
cat -n packages/template-generator/src/post-process/vercel-config.ts | sed -n '1,125p'

Repository: AmanVarshney01/create-better-t-stack

Length of output: 7638


🌐 Web query:

site:vercel.com/docs/project-configuration/vercel-json functions function-matching patterns includeFiles matching function configuration unmatched pattern behavior

💡 Result:

- **Function-config keys** are glob patterns matching function source paths. For example, `api/*.js` matches one level; `api/**/*.ts` matches nested levels. ([vercel.com](https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai))
- **`includeFiles`** is a glob for extra files to bundle with that function; runtime behavior can vary for Community Runtimes. Next.js projects should use `outputFileTracingIncludes` instead. ([vercel.com](https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai))
- **Unmatched function pattern:** Vercel documents this as an error condition—the key’s pattern must match a function source file in the relevant functions directory (with framework-specific paths for Next.js). ([vercel.com](https://vercel.com/docs/errors/error-list))
- **Unresolved:** The docs don’t specify what happens when an `includeFiles` glob itself matches no files. They establish its purpose and pattern type, but not whether an empty match warns, errors, or is silently ignored. ([vercel.com](https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai))

Citations:

- 1: https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai
- 2: https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai
- 3: https://vercel.com/docs/errors/error-list
- 4: https://vercel.com/docs/project-configuration/vercel-json?utm_source=openai

Use the selected entrypoint as the functions key.

For Nest, entrypoint is src/main.ts, but includeFiles is configured under src/index.ts. Vercel requires a function pattern to match a function source file and reports unmatched patterns as errors, so Nest deployments can fail. Keep the key aligned with the selected entrypoint.

🐛 Suggested fix
-        "src/index.ts": {
+        [backend === "nest" ? "src/main.ts" : "src/index.ts"]: {

@modejota
modejota force-pushed the feat/nestjs-backend-integration branch from 8f10d91 to b4b6bee Compare October 4, 2026 15:31
Expose Nest.js in CLI and web stack selection, with runtime, ORM, auth, deployment, and addon compatibility rules.

Refs AmanVarshney01#428
Generate conventional Nest modules, controllers, services, DTOs, entities, and main entrypoints for Node and Bun projects.

Add Prisma and Mongoose TODO support plus Docker and Vercel entrypoint handling.

Refs AmanVarshney01#428
Register EvlogModule and initialize request logging for generated and existing Nest servers.

Closes AmanVarshney01#428
Enable the generated oRPC query providers for Nest TODO projects without an API selection.

Refs AmanVarshney01#428
Move Nest.js rules into the shared compatibility module and stack builder
validation, read server and client env from the per-app env modules, and
use the services module for the database and auth instances. Wire the
evlog dev file system drain for Nest and keep Axiom unsupported.

Refs AmanVarshney01#428
Prefix Nest health and Todo routes with /api when web and server deploy
together on Vercel, matching the rewrite that forwards /api/* to the server.
Key the Vercel function config by the selected server entrypoint.

Refs AmanVarshney01#428
@modejota
modejota force-pushed the feat/nestjs-backend-integration branch from b4b6bee to a6607ad Compare October 4, 2026 16:07
@modejota

modejota commented Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Hi @AmanVarshney01. Sorry to ping you mate. I've updated the PR for the Nest.js integration, in case you can take a look at it. I'm pretty sure that people waiting for this would be very much pleased.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant