docs(static-file): clarify path extraction and wildcard pattern behavior 📝

- Add explanation for using ctx.pathname instead of wildcard parameters
- Document FastRouter wildcard pattern limitation behavior
- Update path resolution steps in documentation
- Fix handler to return instead of throwing when routes directory not found

Author: NeaByteLab

docs/en/static-file/basic.md

@@ -30,10 +30,23 @@ This serves files from the `public/` directory at the `/static` URL path:
 Deserve uses a custom static file serving implementation:
 
 1. **Route Matching**: Creates routes with pattern `${urlPath}/**` to match all files
-2. **File Resolution**: Maps URL paths to file system paths using the `path` option
-3. **Wildcard Capture**: Extracts file path from route parameters (`params['_']`)
+2. **Path Extraction**: Uses `ctx.pathname` directly to get the full request path (FastRouter's `/**` pattern only captures the first segment, so we use pathname instead)
+3. **File Resolution**: Maps URL paths to file system paths using the `path` option
 4. **Priority**: Static routes are registered for all HTTP methods before dynamic routes
 
+### Wildcard Pattern Behavior
+
+When `urlPath` is `/`, Deserve creates a `/**` pattern. For path resolution, Deserve uses `ctx.pathname` instead of relying on wildcard parameter, because:
+
+- FastRouter's `/**` pattern only captures the **first segment** of the request path instead of the full path (e.g., `"styles"` for `/styles/ui.css`)
+- To serve nested files correctly, Deserve extracts the full path from `ctx.pathname` and removes the leading `/` to get the relative file path
+
+**Example:**
+- Request: `GET /styles/ui.css`
+- Pattern: `/**` matches from configurable path
+- File path: Extracted from `ctx.pathname` → `"styles/ui.css"`
+- Resolved: `static/styles/ui.css`
+
 ## Static File Options
 
 The `static()` method accepts a `ServeOptions` object:

docs/id/static-file/basic.md

@@ -30,10 +30,23 @@ Ini menyajikan file dari direktori `public/` di path URL `/static`:
 Deserve menggunakan implementasi custom untuk menyajikan file statis:
 
 1. **Route Matching**: Membuat routes dengan pola `${urlPath}/**` untuk mencocokkan semua file
-2. **File Resolution**: Memetakan URL paths ke file system paths menggunakan opsi `path`
-3. **Wildcard Capture**: Mengekstrak path file dari route parameters (`params['_']`)
+2. **Path Extraction**: Menggunakan `ctx.pathname` langsung untuk mendapatkan full request path (pola `/**` dari FastRouter hanya menangkap segment pertama, jadi kita menggunakan pathname sebagai gantinya)
+3. **File Resolution**: Memetakan URL paths ke file system paths menggunakan opsi `path`
 4. **Priority**: Static routes diregistrasi untuk semua HTTP methods sebelum dynamic routes
 
+### Perilaku Wildcard Pattern
+
+Ketika `urlPath` adalah `/`, Deserve membuat pola `/**`. Untuk path resolution, Deserve menggunakan `ctx.pathname` daripada mengandalkan wildcard parameter, karena:
+
+- Pola `/**` dari FastRouter hanya menangkap **segment pertama** dari request path alih-alih full path (misalnya, `"styles"` untuk `/styles/ui.css`)
+- Untuk menyajikan file nested dengan benar, Deserve mengekstrak full path dari `ctx.pathname` dan menghapus leading `/` untuk mendapatkan relative file path
+
+**Contoh:**
+- Request: `GET /styles/ui.css`
+- Pattern: `/**` cocok dari path yang dikonfigurasi
+- File path: Diekstrak dari `ctx.pathname` → `"styles/ui.css"`
+- Resolved: `static/styles/ui.css`
+
 ## Opsi Static File
 
 Method `static()` menerima objek `ServeOptions`:

src/Handler.ts

@@ -176,7 +176,7 @@ export class Handler {
       }
     } catch (error) {
       if (error instanceof Deno.errors.NotFound) {
-        throw new Error(`Routes directory not found: ${targetDir}`)
+        return
       } else {
         throw error
       }