feat: experimental --next flag for nest-base template#80
Merged
Conversation
…mplate Adds an experimental `--next` option to `lt server create` and `lt fullstack init` that swaps the API template from nest-server-starter (MongoDB) to lenneTech/nest-base (Bun + Prisma 7 + Postgres + Better-Auth). When `--next` is set: - repoUrl points to https://github.com/lenneTech/nest-base.git - API mode is forced to Rest, framework mode is forced to npm - nest-server-starter-specific patching is skipped (config.env.ts, main.ts Swagger, meta.json, lt.config.json, CLAUDE.md API mode) - vendor-mode transformation is skipped - workspace install is skipped in fullstack mode (user runs `pnpm install` for app, `bun install` for api) Tested end-to-end: - `lt server create my-next-server --next --noConfirm` produces a bun-based nest-base project with patched package.json. - `lt fullstack init --name my-next-fs --frontend nuxt --next --noConfirm` produces a workspace with nuxt frontend + nest-base api side-by-side. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds the --next flag to the LT-ECOSYSTEM-GUIDE flags list so the canonical reference is in sync with README and docs/commands.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an experimental
--nextflag tolt server createandlt fullstack initthat swaps the API template fromnest-server-starter(MongoDB) tonest-base— a new NestJS stack on Bun + Prisma 7 + Postgres + Better-Auth with a built-in/devcockpit.What changes
--nextflag on:lt server create my-api --next [--noConfirm] [--description ...] [--author ...]lt fullstack init --name my-app --frontend nuxt --next [--noConfirm]https://github.com/lenneTech/nest-base.gitinstead ofnest-server-starter.apiMode = RestandframeworkMode = npm(other modes don't apply to nest-base).config.env.ts,main.tsSwagger,meta.json, README EJS template, CLAUDE.md API mode).package.json(name, description, version) — universal.README.md: new "Experimental: `--next`" section under Framework consumption modes.docs/commands.md: option tables for `lt server create` and `lt fullstack init` updated.docs/LT-ECOSYSTEM-GUIDE.md: flag added to the canonical flag list.Test plan
Notes
🤖 Generated with Claude Code