Releases: lenneTech/cli
1.22.0
1.20.0
Incremental fullstack workspace + KI-safe standalone gates (1.20.0)
lt fullstack add-api/add-app— incrementally add a missing
half (api or app) to an existing workspace; full flag parity with
init(--api-mode, --framework-mode, --framework-upstream-branch,
--api-branch/copy/link, --next, --dry-run, --skip-install)lt fullstack initauto-delegates to add-api / add-app when run
in a workspace that already has one half present- Standalone scaffolders (
server create,frontend nuxt,
frontend angular) gain --dry-run, --force, and a workspace gate:
refuse loudly when called non-interactively (TTY off OR --noConfirm)
inside a workspace; suggest the matching add-* command - Detection covers npm/yarn/bun workspaces (package.json#workspaces)
and walks up from sub-projects soadd-apiworks from inside
projects/app/src/ lt statusnow reports workspace layout with ✓/✗ marks for
projects/api / projects/app plus a "go up" hint when in a
sub-project- New lib/workspace-integration.ts (8 helpers) + shared
runStandaloneWorkspaceGate replaces ~75 lines of duplicated logic
across the three standalone commands - Tests: 227 jest (+58) including unit tests for all new helpers,
plus 11 bash E2E scenarios in test-incremental-fullstack.sh - Bug fixes: --name flag honoured in server create + frontend
angular (was ignored), --noConfirm closes description/author
prompts in server create, ocr.ts double-destructure regression - Security: npm audit fix — fast-xml-parser 5.5.8 → 5.7.2
(GHSA-gh4j-gqv2-49f6)
1.19.0
v1.18.0
What's Changed
- feat(fullstack init --next): flatten nuxt-base-template into projects/app/ post-clone by @pascal-klesse in #86
Full Changelog: v1.17.0...v1.18.0
v1.17.0
What's Changed
- feat(fullstack init --next): default frontend branch to 'next' on nuxt-base-starter by @pascal-klesse in #84
Full Changelog: v1.16.0...v1.17.0
v1.16.0
v1.16.0
Bug Fixes / DX
-
fullstack init --next: auto-runs
bun run rename <name>inside the scaffoldedprojects/api/directory after the API clone completes (#83)Closes the gap where every `--next` consumer either remembered to manually run `bun run rename my-project` or ended up with a workspace that said "nest-base" everywhere — `package.json`, `README.md`, `portless.yml`, `docker-compose.yml`. The CLI already knows the project name from `--name`, so it does the rename for the user.
Includes a small reset-package.json-name shim because `setupServerForFullstack` already pre-patches `package.json#name` and the rename planner would otherwise short-circuit before touching the other three files.
Failure of the rename step logs a warning and prints the manual retry command but does NOT abort `init` — the workspace is still bootable; the user can re-run rename later.
Tests: 4 new in `tests/fullstack-init-next-rename.test.ts`. Full suite 157/158 passed (1 skipped, pre-existing).
Other commits since v1.15.0
See full changelog.
v1.15.0
v1.15.0
Bug Fixes
-
fullstack init --next: replace stale root README/CLAUDE.md, suppress noisy noConfirm hint (#81)
When
lt fullstack init --nextran, the workspace inherited rootREADME.md+CLAUDE.mdfromlt-monorepodescribing the legacy MongoDB + GraphQL + vendor-mode stack — none of which applies to thenest-basetemplate. The stale files poisoned AI agent context (rootCLAUDE.mdis auto-loaded as repo orientation) and confused human readers.- New
src/templates/next-fullstack/{README,CLAUDE}.md.ejs+.claude/QUICKSTART.md.ejs— minimal, correct content describing the actual Bun + Prisma 7 + Postgres + Better-Auth + REST stack. init.ts: when--next, render the new templates over the cloned root files instead of just patching{{TEMPLATE_VAR}}placeholders.tools.nonInteractiveHint(): skip the yellow hint when caller already passed--noConfirm.__tests__/git-commands.test.ts: stabilise flaky test (`--untracked-files=no` for clean-work-dir check, `hasUpstream` guard for upstream-less branches).
- New
Other commits since v1.14.0
See full changelog.
1.14.0
Add experimental --next flag for lt server create and lt fullstack init that swaps the API template from nest-server-starter (MongoDB) to nest-base — a NestJS stack on Bun + Prisma 7 + Postgres + Better-Auth.
When --next is set, the CLI clones nest-base instead of nest-server-starter, forces apiMode = Rest and frameworkMode = npm, skips starter-specific patching (config.env.ts, Swagger main.ts, meta.json, README EJS, lt.config.json, vendor mode, CLAUDE.md API mode), and skips workspace install in fullstack mode (run pnpm install for app + bun install for api manually).
Downstream lt server module/object/addProp/test/permissions are not yet compatible with the resulting nest-base layout — use --next for greenfield prototyping only.
PR: #80