@alevnyacow/nzmt 0.39.1 → 0.39.3

package/README.md

@@ -295,9 +295,26 @@ Once you done implementing controller methods, just run `nmx nzmt rq`. This comm
 
 # FAQ
 
-## What does DDD-inspired mean?
+## Why not use Nest or tRPC?
+
+`NZMT` combines the best of both worlds in one package while staying in plain Next.js:
+
+| Feature           | NZMT | tRPC | Nest |
+| ----------------- | ---- | ---- | ---- |
+| Type safety       | ✅  - including run-time checks  | ✅    | ⚠️   |
+| Scaffolding       | ✅  - production-ready full-stack  | ❌    | ⚠️   |
+| Architecture      | contract-first, domain-focused | ❌    | module-centric, tightly coupled |
+| Boilerplate       | ✅ - Low  | ✅   | ❌ - High |
+| No framework lock-in | ✅    | ✅    | ❌    |
+| Single source of truth | ✅ (schemas) | ⚠️ (types only) | ❌ |
+| Time to first feature | ✅ instant full-stack | ⚡ fast | 🐢 slow |
+| Learning curve       | Medium | Low | High |
+| Code ownership       | ✅ full (generated, editable) | ✅ | ⚠️ (framework patterns) |
+
+
+## What does domain-focused mean?
 
-NZMT puts your business domain first. Entities drive the architecture, so backend and frontend stay consistent, and all layers are generated from your entity contracts and schemas.
+NZMT puts your business domain first. Entities drive the architecture, so backend and frontend stay consistent.
 
 ## What does contract-first mean?
 
@@ -307,9 +324,9 @@ The behavior of all server modules in NZMT is governed by Zod schemas. Function
 
 Yes — everything is fully editable, including configuration. Think of NZMT as a shadcn-style approach for full-stack: scaffold first, then fully own the code. Moreover, in most of the cases your changes are preserved on subsequent generations. For example, if you modify a generated query and run `npx nzmt rq` later, your edits stay intact.
 
-## Do I really need to understand DI and other fancy concepts to use NZMT?
+## Do I really need to understand DI and other fancy concepts to use NZMT effectively?
 
-No. NZMT handles dependency injection (DI) for you using `inversifyjs`. You don’t need to set it up manually.
+Not really. NZMT handles dependency injection (DI) for you using `inversifyjs`. You don’t need to set it up manually.
 To get an instance of a service anywhere in your server code, just use:
 
 ```tsx
@@ -322,16 +339,4 @@ Here, `fromDI` is strongly typed — your IDE will give autocomplete automatical
 
 ## Why data layer modules are called `Stores` and not `Repositories`?
 
-A “Repository” is a specific design pattern for managing data. NZMT prefers Stores — a simple, flexible abstraction for your data layer that can adapt to your needs regardless of the specific pattern. This approach helps to keep your code simple, and it has been successfully used in other languages, like Go.
-
-## Why not use Nest or tRPC?
-
-`NZMT` combines the best of both worlds in one package while staying in plain Next.js:
-
-| Feature           | NZMT | tRPC | Nest |
-| ----------------- | ---- | ---- | ---- |
-| Type safety       | ✅    | ✅    | ⚠️   |
-| Scaffolding       | ✅    | ❌    | ⚠️   |
-| Architecture      | ✅    | ❌    | ✅    |
-| Boilerplate       | Low  | Low  | High |
-| No framework lock-in | ✅    | ✅    | ❌    |
+A “Repository” is a specific design pattern for managing data. NZMT prefers Stores — a simple, flexible abstraction for your data layer that can adapt to your needs regardless of the specific pattern. This approach helps to keep your code simple, and it has been successfully used in other languages, like Go.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alevnyacow/nzmt",
-  "version": "0.39.1",
+  "version": "0.39.3",
   "description": "Next Zod Modules Toolkit",
   "keywords": ["next", "full-stack", "server", "backend", "cli", "scaffolding", "zod", "rest", "contract programming", "contract-first", "react-query", "ddd", "domain-driven"],
   "repository": {