lapeh 2.2.7 → 2.2.8

package/bin/index.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 const fs = require('fs');
 const path = require('path');
@@ -37,10 +37,14 @@ function runDev() {
     const tsNodePath = require.resolve('ts-node/register');
     const tsConfigPathsPath = require.resolve('tsconfig-paths/register');
     
-    // Resolve bootstrap file relative to this script
-    // If run from node_modules, it will find ../lib/bootstrap.ts
-    // If run from source, it will find ../lib/bootstrap.ts
-    const bootstrapPath = path.resolve(__dirname, '../lib/bootstrap.ts');
+    // Resolve bootstrap file
+    // 1. Try to find it in the current project's node_modules (preferred)
+    const localBootstrapPath = path.join(process.cwd(), 'node_modules/lapeh/lib/bootstrap.ts');
+    
+    // 2. Fallback to relative to this script (if running from source or global cache without local install)
+    const fallbackBootstrapPath = path.resolve(__dirname, '../lib/bootstrap.ts');
+    
+    const bootstrapPath = fs.existsSync(localBootstrapPath) ? localBootstrapPath : fallbackBootstrapPath;
 
     // We execute a script that requires ts-node to run lib/bootstrap.ts
     execSync(`npx nodemon --watch src --watch lib --ext ts,json --exec "node -r ${tsNodePath} -r ${tsConfigPathsPath} ${bootstrapPath}"`, { stdio: 'inherit' });
@@ -210,11 +214,35 @@ async function upgradeProject() {
 function createProject() {
   const projectName = args.find(arg => !arg.startsWith('-'));
   const isFull = args.includes('--full');
-  const useDefaults = args.includes('--defaults');
+  // Allow -y alias for --defaults
+  const useDefaults = args.includes('--defaults') || args.includes('-y');
+
+  // Helper to parse arguments like --key=value
+  const getArg = (key) => {
+    const prefix = `--${key}=`;
+    const arg = args.find(a => a.startsWith(prefix));
+    return arg ? arg.substring(prefix.length) : undefined;
+  };
+
+  const dbTypeArg = getArg('db-type');
+  const dbHostArg = getArg('db-host');
+  const dbPortArg = getArg('db-port');
+  const dbUserArg = getArg('db-user');
+  const dbPassArg = getArg('db-pass');
+  const dbNameArg = getArg('db-name');
 
   if (!projectName) {
     console.error('❌ Please specify the project name:');
-    console.error('   npx lapeh-cli <project-name> [--full]');
+    console.error('   npx lapeh-cli <project-name> [--full] [--defaults|-y]');
+    console.error('   Options:');
+    console.error('     --full        : Run full setup including seed and dev server');
+    console.error('     --defaults, -y: Use default configuration (can be overridden with args)');
+    console.error('     --db-type=    : pgsql | mysql');
+    console.error('     --db-host=    : Database host');
+    console.error('     --db-port=    : Database port');
+    console.error('     --db-user=    : Database user');
+    console.error('     --db-pass=    : Database password');
+    console.error('     --db-name=    : Database name');
     console.error('   OR');
     console.error('   npx lapeh-cli upgrade (inside existing project)');
     process.exit(1);
@@ -271,12 +299,32 @@ function createProject() {
 
     if (useDefaults) {
       console.log("ℹ️  Using default configuration (--defaults)...");
+      
+      // Default to PostgreSQL
       dbType = { key: "pgsql", label: "PostgreSQL", provider: "postgresql", defaultPort: "5432" };
       host = "localhost";
       port = "5432";
-      user = "postgres"; // Default postgres user is usually postgres, not root
-      password = "password"; // Default password
+      user = "postgres";
+      password = "password";
       dbName = projectName.replace(/-/g, '_');
+
+      // Override with CLI args
+      if (dbTypeArg) {
+         if (dbTypeArg.toLowerCase() === 'mysql') {
+             dbType = { key: "mysql", label: "MySQL", provider: "mysql", defaultPort: "3306" };
+             port = "3306"; 
+         } else if (dbTypeArg.toLowerCase() === 'pgsql') {
+             dbType = { key: "pgsql", label: "PostgreSQL", provider: "postgresql", defaultPort: "5432" };
+             port = "5432";
+         }
+      }
+      
+      if (dbHostArg) host = dbHostArg;
+      if (dbPortArg) port = dbPortArg;
+      if (dbUserArg) user = dbUserArg;
+      if (dbPassArg) password = dbPassArg;
+      if (dbNameArg) dbName = dbNameArg;
+
     } else {
       dbType = await selectOption("Database apa yang akan digunakan?", [
         { key: "pgsql", label: "PostgreSQL", provider: "postgresql", defaultPort: "5432" },
@@ -378,6 +426,7 @@ function createProject() {
     // Update scripts to use lapeh binary
     packageJson.scripts = {
       ...packageJson.scripts,
+      "postinstall": "node scripts/compile-schema.js && prisma generate",
       "dev": "lapeh dev",
       "start": "lapeh start",
       "build": "lapeh build",
@@ -399,6 +448,9 @@ function createProject() {
         tsconfig.compilerOptions.paths["@lapeh/*"] = ["./node_modules/lapeh/lib/*"];
       }
 
+      // Add baseUrl
+      tsconfig.compilerOptions.baseUrl = ".";
+
       // Add ts-node ignore configuration
       tsconfig["ts-node"] = {
         "ignore": ["node_modules/(?!lapeh)"]
@@ -501,14 +553,113 @@ function createProject() {
       console.log('   Compiling schema...');
       execSync('node scripts/compile-schema.js', { cwd: projectDir, stdio: 'inherit' });
       
-      console.log('   Generating Prisma Client...');
-      execSync('npx prisma generate', { cwd: projectDir, stdio: 'inherit' });
-
       // Try to migrate (this will create the DB if it doesn't exist)
       console.log('   Running migration (creates DB if missing)...');
       execSync('npx prisma migrate dev --name init_setup', { cwd: projectDir, stdio: 'inherit' });
       
-      // Seed
+      // Seed (Users & Roles are mandatory, Pets are demo data)
+      console.log('   Seeding mandatory data (Users, Roles, Permissions)...');
+      // Always seed mandatory data by default or check if --full is meant for demo data only?
+      // Based on user request: "user seeder dan pets itu selalu ada karena default, jadi seharusnya tidak digenerate saat user buat project baru"
+      // Wait, user says: "user seeder and pets are always there because default, so it SHOULD NOT be generated when user creates new project, UNLESS user starts using framework and adding new tables"
+      
+      // Interpretation: The user implies that `prisma generate` and `prisma migrate` (which creates the physical tables and client code)
+      // MIGHT be redundant if the core framework already provides a pre-built client for the default models (Users, Pets).
+      // However, Prisma doesn't work like that easily because the Client is generated into node_modules/@prisma/client.
+      
+      // If the user means "don't run migration/seed unless needed", we still need to run them to have a working app.
+      // Re-reading carefully: "masalahnya user seeder dan pets itu selalu ada karane default ,jadi seharusnya tidak digenerate saat user buuat project baru , kecuali user mulai menggunakan framework ini dan menambahkan table baru untuk developmen"
+      
+      // AH! The user might mean: Since User/Pets are CORE models, the Prisma Client for them should ALREADY exist or be pre-packaged, 
+      // so we don't need to run `prisma generate` during project creation?
+      // OR: The user means the *migration files* shouldn't be generated?
+      
+      // "seharusnya tidak digenerate saat user buuat project baru" -> The user is annoyed by the `prisma generate` and `migration` step taking time?
+      // But we need the DB tables.
+      
+      // Let's assume the user wants to SKIP the `prisma generate` and `migrate` step if possible, 
+      // but that's impossible for a fresh project connecting to a fresh DB.
+      
+      // Alternative interpretation: The user thinks `prisma generate` is only for NEW tables. 
+      // But `prisma generate` is required to create the client library itself.
+      
+      // Let's look at the "Pets" part. Maybe the user considers Pets as "bloat" that shouldn't be there by default?
+      // "user seeder dan pets itu selalu ada karane default"
+      
+      // Wait, maybe the user is saying: "Since these are default, why do we need to RE-generate/RE-migrate them every time? Can't we just have them ready?"
+      // Answer: No, because every user has a different DB connection string.
+      
+      // Let's explain this to the user. Prisma Client is NOT a static library like `lodash`. It is generated based on the schema.
+      // If we don't generate it, `import { prisma }` will fail because `node_modules/@prisma/client` will be empty.
+      
+      // However, we CAN optimize.
+      // Maybe the user is asking: "Why do we generate migration files (`prisma/migrations`) for default tables?"
+      // We can ship the project WITH the migration folder for the default tables already there!
+      // If we include `prisma/migrations` in the template, `prisma migrate dev` will see they exist and just apply them, 
+      // instead of creating a NEW migration `init_setup`.
+      
+      // Let's try to verify if `prisma/migrations` is in the ignore list.
+      // Line 367: `'prisma/migrations', // Exclude existing migrations`
+      // Yes, we are explicitly excluding them!
+      
+      // If we INCLUDE the base migrations in the template, then we don't need to create a new migration on init.
+      // We just run `prisma migrate deploy` (faster) or `dev` (which will see it's in sync).
+      
+      // Let's change the strategy:
+      // 1. Remove `prisma/migrations` from ignore list.
+      // 2. But wait, the user's template might have dirty migrations.
+      
+      // Let's assume the user wants me to explain/fix the perception.
+      // But wait, the user says "seharusnya tidak digenerate".
+      
+      // Let's stick to the most robust interpretation:
+      // The user wants to avoid the overhead of generation for default stuff.
+      // But generation is fast (ms). Migration is slow.
+      
+      // If the user means the `seed` data (Pets/Users):
+      // "user seeder dan pets itu selalu ada... jadi seharusnya tidak digenerate"
+      // Maybe the user means: Don't SEED them by default?
+      // "kecuali user mulai menggunakan framework ini dan menambahkan table baru"
+      
+      // Let's assume the user is talking about the `prisma generate` process being redundant for default models.
+      // I need to explain that it IS required.
+      
+      // BUT, I can make the process cleaner.
+      // If I look at the previous context: "postinstall" script.
+      // The user is replying to my explanation about "postinstall".
+      
+      // User: "The default models (User/Pets) are always there. So they shouldn't need generation when creating a project. Generation should only happen when I add NEW tables."
+      
+      // This is a misunderstanding of how Prisma works. 
+      // Prisma Client is NOT installed via npm registry with the models pre-baked.
+      // It is an empty shell that fills itself when you run `prisma generate`.
+      
+      // My previous explanation might have been unclear.
+      // I should clarify: "Generate is mandatory to install the library itself".
+      
+      // HOWEVER, maybe I can PRE-GENERATE it?
+      // No, because it depends on the OS/Architecture of the user's machine.
+      
+      // Let's try to satisfy the user's request by skipping the explicit `prisma generate` step in the CLI 
+      // IF we rely on `prisma migrate dev` to do it automatically (it does generate client under the hood).
+      // Line 557: `execSync('npx prisma generate'...)`
+      // Line 561: `execSync('npx prisma migrate dev'...)` -> This AUTOMATICALLY runs generate.
+      
+      // So line 557 is redundant! removing it speeds things up and reduces "generation" noise.
+      
+      // Also, about "seeder":
+      // "seharusnya tidak digenerate saat user buuat project baru"
+      // If the user means the SEED FILE content.
+      // We are copying `prisma/seed.ts` from template.
+      
+      // Let's remove the redundant `prisma generate` call in line 557.
+      // And I will explain to the user WHY generation is still needed (internally) but I removed the explicit step.
+      
+      // Wait, if I remove `prisma generate`, `node scripts/compile-schema.js` must run before migrate.
+      // It does (Line 554).
+      
+      // Let's remove the explicit `prisma generate` logging and command.
+      
       if (isFull) {
         console.log('   Seeding database...');
         execSync('npm run db:seed', { cwd: projectDir, stdio: 'inherit' });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lapeh",
-  "version": "2.2.7",
+  "version": "2.2.8",
   "description": "Framework API Express yang siap pakai (Standardized)",
   "main": "index.js",
   "bin": {
@@ -88,10 +88,7 @@
     "winston": "^3.19.0",
     "winston-daily-rotate-file": "^5.0.0",
     "zod": "3.23.8",
-    "prisma": "7.2.0"
-  },
-  "devDependencies": {
-    "@eslint/js": "^9.39.2",
+    "prisma": "7.2.0",
     "@types/bcryptjs": "2.4.6",
     "@types/compression": "^1.8.1",
     "@types/cors": "2.8.19",
@@ -100,7 +97,10 @@
     "@types/multer": "^2.0.0",
     "@types/node": "25.0.3",
     "@types/pg": "8.16.0",
-    "@types/uuid": "10.0.0",
+    "@types/uuid": "10.0.0"
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.39.2",
     "eslint": "^9.39.2",
     "globals": "^16.5.0",
     "typescript-eslint": "^8.50.1"

package/api-testing-sepuluh/.env.example

@@ -1,19 +0,0 @@
-PORT=8000
-DATABASE_PROVIDER="postgresql"
-DATABASE_URL="postgresql://sianu:12341234@localhost:5432/db_example_test?schema=public"   
-
-# Used for all encryption-related tasks in the framework (JWT, etc.)
-JWT_SECRET="replace_this_with_a_secure_random_string"
-
-# Framework Timezone
-TZ="Asia/Jakarta"
-
-# Redis Configuration (Optional)
-# If REDIS_URL is not set or connection fails, the framework will automatically 
-# switch to an in-memory Redis mock (bundled). No installation required for development.
-# REDIS_URL="redis://lapeh:12341234@localhost:6379"
-# NO_REDIS="true"
-
-# To force disable Redis and use in-memory mock even if Redis is available:
-# NO_REDIS="true"
-

package/api-testing-sepuluh/doc/ARCHITECTURE_GUIDE.md

@@ -1,73 +0,0 @@
-# Panduan Arsitektur: Menuju "Framework as a Dependency" (Next.js Style)
-
-Saat ini, Lapeh menggunakan pendekatan **Boilerplate** (seperti Laravel), di mana pengguna mendapatkan seluruh kode sumber (`src/`) dan bertanggung jawab atas `express`, `prisma`, dll.
-
-Untuk mengubahnya menjadi seperti **Next.js** (di mana pengguna hanya menginstall `lapeh` dan `package.json` mereka bersih), kita perlu mengubah arsitektur menjadi **Library**.
-
-## 1. Perbedaan Utama
-
-| Fitur | Boilerplate (Lapeh Saat Ini) | Library (Next.js Style) |
-| :--- | :--- | :--- |
-| **Instalasi** | `git clone` / `npx create-lapeh` | `npm install lapeh` |
-| **package.json** | Banyak dependency (`express`, `cors`, dll) | Sedikit (`lapeh`, `react`) |
-| **Scripts** | Panjang (`nodemon src/index.ts`) | Pendek (`lapeh dev`) |
-| **Core Code** | Terbuka di `src/core/` | Tersembunyi di `node_modules/lapeh` |
-| **Update** | Susah (harus merge manual) | Mudah (`npm update lapeh`) |
-
-## 2. Langkah Implementasi
-
-Saya telah memulai langkah pertama dengan menambahkan **CLI Runner** di `bin/index.js`.
-
-### A. Update CLI (`bin/index.js`) ✅ (Sudah Dilakukan)
-Saya sudah menambahkan command `dev`, `start`, dan `build` ke dalam CLI Lapeh. Ini memungkinkan pengguna menjalankan server tanpa tahu perintah aslinya.
-
-```javascript
-// Contoh penggunaan nanti:
-"scripts": {
-  "dev": "lapeh dev",
-  "build": "lapeh build",
-  "start": "lapeh start"
-}
-```
-
-### B. Struktur Project Pengguna (Target)
-Nantinya, project pengguna Lapeh hanya akan berisi file bisnis mereka:
-
-```text
-my-app/
-├── src/
-│   ├── controllers/
-│   ├── routes/
-│   └── models/
-├── lapeh.config.ts  <-- Konfigurasi framework (pengganti edit core)
-└── package.json
-```
-
-Dan `package.json` mereka akan terlihat seperti ini:
-
-```json
-{
-  "name": "my-app",
-  "dependencies": {
-    "lapeh": "^2.0.0"
-  },
-  "scripts": {
-    "dev": "lapeh dev",
-    "build": "lapeh build",
-    "start": "lapeh start"
-  }
-}
-```
-
-### C. Apa yang Harus Dilakukan Selanjutnya?
-
-1.  **Publish Package**: Anda perlu mempublish folder framework ini ke NPM (atau private registry).
-    *   Pastikan `express`, `cors`, `helmet`, dll ada di `dependencies` (bukan `devDependencies`).
-2.  **Abstraksi `src/index.ts`**:
-    *   Saat ini `src/index.ts` adalah entry point yang diedit user.
-    *   Ubah agar `lapeh dev` menjalankan server internal yang **mengimpor** routes/controller user secara dinamis (seperti Next.js pages router).
-3.  **Config Loader**:
-    *   Buat sistem pembacaan `lapeh.config.ts` untuk mengatur Port, Database URL, dll tanpa mengedit kode core.
-
-## 3. Kesimpulan
-Perubahan yang saya lakukan di `bin/index.js` adalah fondasi untuk CLI style. Untuk mencapai "Clean package.json" sepenuhnya, Anda harus memisahkan **Framework Core** (repo ini) dengan **User Project** (repo baru yang menginstall framework ini).

package/api-testing-sepuluh/doc/CHANGELOG.md

@@ -1,77 +0,0 @@
-# Dokumentasi Perubahan Lapeh Framework
-
-File ini mencatat semua perubahan, pembaruan, dan perbaikan yang dilakukan pada framework Lapeh, diurutkan berdasarkan tanggal.
-
-## [2025-12-27] - Code Quality & Standardization Update
-
-### 🚀 Fitur & Standarisasi
-
-- **Standardized Import Paths**:
-  - Implementasi path alias `@/` untuk import yang lebih bersih (e.g., `import { prisma } from "@/core/database"`).
-  - Penghapusan penggunaan relative paths yang dalam (`../../../`).
-  - Konfigurasi `tsconfig.json` tanpa `baseUrl` (mengikuti standar TypeScript 6.0+).
-- **Strict Linting & Code Quality**:
-  - Implementasi aturan **ESLint** ketat untuk mencegah "Dead Code".
-  - Error otomatis untuk variabel, parameter, dan import yang tidak digunakan (`no-unused-vars`).
-  - Script `npm run lint` dan `npm run lint:fix` untuk pembersihan kode otomatis.
-- **Fastify-Style Standardization**:
-  - Penerapan standar respon cepat (`sendFastSuccess`) di seluruh controller (`AuthController`, `RbacController`, `PetController`).
-  - Penggunaan **Schema-based Serialization** untuk performa JSON maksimal.
-  - Konversi otomatis `BigInt` ke `string` dalam respon JSON.
-
-## [2025-12-27] - High Performance & Scalability Update
-
-### 🚀 Fitur Baru
-
-- **High Performance Serialization (Fastify-Style)**:
-  - Implementasi `fast-json-stringify` untuk serialisasi JSON super cepat (2x-3x lebih cepat dari `JSON.stringify`).
-  - Helper `sendFastSuccess` di `src/utils/response.ts` untuk mem-bypass overhead Express.
-  - Caching schema serializer otomatis di `src/core/serializer.ts`.
-- **Scalability & Clustering**:
-  - Dukungan **Load Balancing** dengan Nginx.
-  - Dukungan **Redis Clustering** untuk Rate Limiter (`rate-limit-redis`).
-  - File konfigurasi `docker-compose.cluster.yml` untuk simulasi cluster lokal (1 Nginx + 2 App Instances + 1 Redis).
-- **Smart Error Handling**:
-  - Deteksi otomatis port bentrok (`EADDRINUSE`) saat startup.
-  - Memberikan saran command _copy-paste_ untuk mematikan process yang memblokir port (support Windows, Mac, Linux).
-- **SEO Optimization**:
-  - Update metadata `package.json` dan `README.md` agar framework lebih mudah ditemukan di Google/NPM.
-
-## [2025-12-27] - Pembaruan Struktur & Validasi
-
-### 🚀 Fitur Baru
-
-- **Laravel-style Validator**:
-  - Implementasi utility `Validator` baru di `src/utils/validator.ts` yang meniru gaya validasi Laravel.
-  - Mendukung rule string seperti `required|string|min:3|email`.
-  - Penambahan rule `unique` untuk pengecekan database otomatis (Prisma).
-  - Penambahan rule `mimes`, `image`, `max` (file size) untuk validasi upload file.
-  - Penambahan rule `sometimes` untuk field opsional.
-- **Framework Hardening (Keamanan & Stabilitas)**:
-  - **Rate Limiting**: Middleware anti-spam/brute-force di `src/middleware/rateLimit.ts`.
-  - **Request Logger**: Pencatatan log request masuk di `src/middleware/requestLogger.ts`.
-  - **Health Check**: Endpoint `/` kini mengembalikan status kesehatan server.
-  - **Graceful Shutdown**: Penanganan penutupan koneksi Database dan Redis yang aman saat server berhenti (`SIGTERM`/`SIGINT`).
-  - **Environment Validation**: Validasi variabel `.env` wajib (seperti `DATABASE_URL`, `JWT_SECRET`) saat startup.
-- **Struktur Folder Baru**:
-  - Pemisahan konfigurasi inti ke `src/core/` (`server.ts`, `database.ts`, `redis.ts`, `realtime.ts`) agar folder `src` lebih bersih.
-  - Sentralisasi route di `src/routes/index.ts` (WIP).
-- **CLI Improvements**:
-  - `npx lapeh <project-name> --full` kini otomatis menjalankan server dev setelah instalasi selesai, sehingga user bisa langsung melihat hasil tanpa mengetik perintah tambahan.
-
-### 🛠️ Perbaikan & Refactoring
-
-- **Controller Refactoring**:
-  - `AuthController`: Migrasi ke `Validator` baru, termasuk validasi upload avatar.
-  - `PetController`: Migrasi ke `Validator` baru.
-  - `RbacController`: Migrasi sebagian ke `Validator` baru.
-- **Pembersihan**:
-  - Penghapusan folder `src/schema/` (Zod schema lama) karena sudah digantikan oleh `Validator` utility.
-  - Penghapusan file duplikat/lama di root `src/` setelah migrasi ke `src/core/`.
-
-### 📝 Catatan Teknis
-
-- **Validator Async**: Method `fails()`, `passes()`, dan `validated()` kini bersifat `async` untuk mendukung pengecekan database (`unique`).
-- **Type Safety**: Semua perubahan telah diverifikasi dengan `npm run typecheck`.
-
----

package/api-testing-sepuluh/doc/CHEATSHEET.md

@@ -1,94 +0,0 @@
-# Lapeh Framework Cheatsheet
-
-Referensi cepat untuk perintah dan kode yang sering digunakan.
-
-## 💻 CLI Commands
-
-| Perintah                             | Fungsi                                       |
-| :----------------------------------- | :------------------------------------------- |
-| **`npm run dev`**                    | Menjalankan server development (hot-reload). |
-| **`npm run typecheck`**              | Cek error TypeScript (tanpa compile).        |
-| **`npm run lint`**                   | Cek kode kotor/variabel tidak terpakai.      |
-| **`npm run lint:fix`**               | Perbaiki kode kotor otomatis.                |
-| **`npm run make:module <Name>`**     | Buat Controller, Route, & Model sekaligus.   |
-| **`npm run make:controller <Name>`** | Buat Controller saja.                        |
-| **`npm run make:model <Name>`**      | Buat Model Prisma saja.                      |
-| **`npm run prisma:migrate`**         | Apply perubahan schema ke DB lokal.          |
-| **`npm run db:studio`**              | Buka GUI Database.                           |
-| **`npm run db:seed`**                | Isi data dummy.                              |
-| **`npm run db:reset`**               | Hapus DB & mulai dari nol.                   |
-
-## 🛡️ Validator Rules (Laravel-Style)
-
-Gunakan di `Validator.make(data, rules)`.
-
-| Rule               | Deskripsi               | Contoh                              |
-| :----------------- | :---------------------- | :---------------------------------- | -------- |
-| `required`         | Wajib ada & tidak null. | `"required"`                        |
-| `string`           | Harus text.             | `"required                          | string"` |
-| `number`           | Harus angka.            | `"required                          | number"` |
-| `email`            | Format email valid.     | `"required                          | email"`  |
-| `min:X`            | Min panjang/nilai.      | `"min:8"` (pass), `"min:18"` (umur) |
-| `max:X`            | Max panjang/nilai.      | `"max:255"`                         |
-| `unique:table,col` | Cek unik di DB.         | `"unique:users,email"`              |
-| `exists:table,col` | Cek exist di DB.        | `"exists:roles,id"`                 |
-| `image`            | File harus gambar.      | `"required                          | image"`  |
-| `mimes:types`      | File extension.         | `"mimes:pdf,docx"`                  |
-
-## 🔑 Authentication
-
-**Middleware di Route:**
-
-```typescript
-import { requireAuth, requireAdmin } from "@/middleware/auth";
-
-router.get("/profile", requireAuth, getProfile); // Login User
-router.delete("/user", requireAuth, requireAdmin, del); // Admin Only
-```
-
-**Akses User di Controller:**
-
-```typescript
-// (req as any).user tersedia setelah requireAuth
-const userId = (req as any).user.userId;
-const role = (req as any).user.role;
-```
-
-## ⚡ Fast Response (Serializer)
-
-**1. Schema:**
-
-```typescript
-const schema = {
-  type: "object",
-  properties: {
-    id: { type: "string" },
-    name: { type: "string" },
-  },
-};
-```
-
-**2. Serializer:**
-
-```typescript
-const serializer = getSerializer("key-name", createResponseSchema(schema));
-```
-
-**3. Send:**
-
-```typescript
-sendFastSuccess(res, 200, serializer, { ...data });
-```
-
-## 📦 Redis (Cache)
-
-```typescript
-import { redis } from "@lapeh/core/redis";
-
-// Set Cache (Key, Value, Mode, Detik)
-await redis.set("profile:1", JSON.stringify(data), "EX", 3600);
-
-// Get Cache
-const cached = await redis.get("profile:1");
-if (cached) return JSON.parse(cached);
-```

package/api-testing-sepuluh/doc/CLI.md

@@ -1,106 +0,0 @@
-# CLI Tools & Scripts
-
-Lapeh Framework dilengkapi dengan berbagai script CLI untuk mempercepat proses development, mulai dari generate code hingga manajemen database.
-
-Semua perintah dijalankan menggunakan `npm run <command>`.
-
-## Code Generators
-
-Gunakan perintah ini untuk membuat file boilerplate secara otomatis.
-
-### 1. Membuat Module Lengkap (`make:module`)
-Membuat Controller, Route, dan Model (Schema) sekaligus.
-
-```bash
-npm run make:module <nama-module>
-```
-**Contoh:** `npm run make:module Product`
-
-Output:
-- `src/controllers/productController.ts`
-- `src/routes/product.ts`
-- `src/models/product.prisma`
-
-### 2. Membuat Controller (`make:controller`)
-Hanya membuat file controller dengan method CRUD dasar.
-
-```bash
-npm run make:controller <nama-controller>
-```
-**Contoh:** `npm run make:controller Order` (Akan membuat `src/controllers/orderController.ts`)
-
-### 3. Membuat Model Database (`make:model`)
-Hanya membuat file schema Prisma baru.
-
-```bash
-npm run make:model <nama-model>
-```
-**Contoh:** `npm run make:model Transaction` (Akan membuat `src/models/transaction.prisma`)
-
-## Database Management (Prisma)
-
-Framework ini menggunakan sistem **Multi-File Schema**. Anda tidak mengedit `schema.prisma` secara langsung, melainkan mengedit file kecil di `src/models/*.prisma`.
-
-### 1. Migrasi Database (`prisma:migrate`)
-Jalankan setiap kali Anda mengubah definisi model di `src/models/*.prisma`.
-
-```bash
-npm run prisma:migrate
-```
-Perintah ini akan:
-1. Menggabungkan semua file `.prisma` di `src/models/` menjadi satu `prisma/schema.prisma`.
-2. Membuat file migrasi SQL.
-3. Menerapkan perubahan ke database lokal.
-4. Men-generate ulang Prisma Client (Type Definitions).
-
-### 2. Deploy ke Production (`prisma:deploy`)
-Gunakan di server production. Hanya menerapkan migrasi yang sudah ada tanpa reset data.
-
-```bash
-npm run prisma:deploy
-```
-
-### 3. Database Studio (`db:studio`)
-Membuka GUI di browser untuk melihat dan mengedit data database.
-
-```bash
-npm run db:studio
-```
-
-### 4. Seeding Data (`db:seed`)
-Mengisi database dengan data awal yang didefinisikan di `prisma/seed.ts`.
-
-```bash
-npm run db:seed
-```
-
-### 5. Reset Database (`db:reset`)
-**PERINGATAN:** Menghapus semua data dan tabel, lalu menjalankan migrasi dari awal.
-
-```bash
-npm run db:reset
-```
-
-## Code Quality & Utilities
-
-### 1. Linting (`lint`)
-Memeriksa kode dari error, variabel tidak terpakai, dan gaya penulisan.
-
-```bash
-npm run lint
-```
-Gunakan `npm run lint:fix` untuk memperbaiki error otomatis.
-
-### 2. Type Check (`typecheck`)
-Memeriksa error tipe data TypeScript tanpa melakukan compile.
-
-```bash
-npm run typecheck
-```
-
-### 3. Generate JWT Secret (`generate:jwt`)
-Membuat random string aman untuk `JWT_SECRET` di file `.env`.
-
-```bash
-npm run generate:jwt
-```