Skip to content

Releases: Aitaouss/StackForge

v1.5.2 — Resource numeric fields + reliable pnpm dev

Choose a tag to compare

@Aitaouss Aitaouss released this 24 Sep 14:31
998bb4f

Summary

Patch release for generated apps and stackforge g resource: numeric Prisma/Zod field types, safer field names, and fixes so pnpm dev works on fresh scaffolds without manual Nest config edits.
Install: npx create-stackforge-app@1.5.2 my-app -y
Upgrade existing projects: pnpm add -D create-stackforge-app@1.5.2

New in 1.5.2 — g resource field types

--field now supports:

Type Aliases Prisma
string String
int integer Int
float number Float
decimal Decimal
All fields remain :required in this release.
Field names may include _ (e.g. media_impressions:int:required).
Example:
pnpm exec stackforge g resource media --dry-run \
  --field medianame:string:required \
  --field media_impressions:int:required \
  --field influencer:string:required

Then migrate and build contracts:

pnpm --filter ./apps/api exec prisma migrate dev --name add_media
pnpm --filter ./packages/contracts run build

Included from 1.5.1 — Nest dev on new projects

  • nest start --watch no longer clears dist/ without recompiling (deleteOutDir: false)
  • Removed TypeScript incremental from shared Nest tsconfig
  • Root .gitignore includes *.tsbuildinfo

Reminder (1.5.0)

  • stackforge generate resource / g resource — Prisma + Nest + packages/contracts
  • Root script: pnpm run generate -- resource <name>
  • Built-in defaults for post (title, content); other names need --field
  • API-only MVP (no web UI for new resources)

Requirements

  • pnpm required for install and monorepo scripts (corepack enable or install pnpm globally)
  • Use --no-install on create if pnpm is not set up yet, then run pnpm install in the project

Docs

create-stackforge-app 1.4.2

Choose a tag to compare

@Aitaouss Aitaouss released this 22 Sep 10:45
ad2a7dc

Highlights

  • Prisma client — automatic generation via postinstall, predev, and prebuild; Docker builders generate after the schema is copied (lifecycle
    scripts ignored where needed).
  • pnpm run db:setup — generate + dev migrations from the project root.
  • pnpm run doctor / pnpm run info — via create-stackforge-app@^1.4.1 dev dependency (plain npx stackforge is not supported).
  • Docs — clearer PostgreSQL setup order; separate local-dev vs full-Docker paths; configurable Compose host ports (same defaults).
  • CI — Docker smoke tests avoid host port collisions; smoke covers auto Prisma + generated diagnostics.

Install

npx create-stackforge-app@1.4.2 my-app -y
pnpm dlx create-stackforge-app@1.4.2 my-app -y

Upgrade note

Existing projects scaffolded before 1.4.2 do not get these scripts automatically. Scaffold a fresh app or copy the root package.json scripts from a
1.4.2 project. See docs/tested-stack.md.
Full diff: v1.4.1...v1.4.2

v1.4.1

Choose a tag to compare

@Aitaouss Aitaouss released this 21 Sep 17:17
8a9dfd8

create-stackforge-app 1.4.1

Patch release: Docker and Prisma Studio fixes for generated apps with packages/contracts.

Fixes

  • Web Docker build: prod install no longer runs contracts prepare/tsc without TypeScript; build contracts in the builder and copy dist into
    the runner with --ignore-scripts.
  • Prisma Studio in Docker: dedicated studio image stage; Postgres URL uses sslmode=disable; Studio bound to 127.0.0.1:5555.
  • API image: clean prod-deps stage instead of pruning the full dev install tree.
  • Local dev: predev + contracts watcher in pnpm dev (no unsafe root postinstall).

Install

npx create-stackforge-app@1.4.1

PR