https://docs-deserve.neabyte.com/by-design/bearer-auth2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/bearer-auth2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/cache2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/cache2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/compress2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/compress2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/https-redirect2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/https-redirect2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/locale-redirect2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/locale-redirect2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/method-override2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/method-override2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/pretty-json2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/pretty-json2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/rate-limit2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/rate-limit2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/request-id2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/request-id2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/server-timing2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/server-timing2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/tracing2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/tracing2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/by-design/xss2026-06-09T10:15:08.000Zhttps://docs-deserve.neabyte.com/id/by-design/xss2026-06-09T10:23:42.000Zhttps://docs-deserve.neabyte.com/core-concepts/context-object2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/core-concepts/context-object2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/core-concepts/file-based-routing2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/core-concepts/file-based-routing2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/core-concepts/hot-reload2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/hot-reload-principles.pngAn abstract view of why reloading stays safe, where applying a file change live rests on three mechanisms that hold together, isolating each file with a try catch so a bad one never crashes the others, busting the module cache with a timestamp query so stale code never contaminates the new, and reloading in sequence by removing then registering after a debounce, which together deliver live edits with no downtime, no crash, and no contaminationhttps://docs-deserve.neabyte.com/diagrams/hot-reload-route-sequence.pngThe route reload sequence as the watcher runs it, where Deno.watchFs detects a change and debounces for 150ms, FastRouter.remove drops the old pattern, the module is re-imported with a timestamp query to bypass the cache, then it is validated for an HTTP method and its handlers register while emitting route:reloaded, and any failure in that step instead emits reload:error so the server stays alive and other routes are unaffectedhttps://docs-deserve.neabyte.com/id/core-concepts/hot-reload2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/hot-reload-principles.pngPandangan abstrak kenapa reload tetap aman, di mana menerapkan perubahan berkas secara live bertumpu pada tiga mekanisme yang berpegangan bersama, mengisolasi tiap berkas dengan try catch agar yang buruk tak pernah membuat yang lain crash, membuang cache modul dengan query timestamp agar kode basi tak pernah mengontaminasi yang baru, dan memuat ulang secara berurutan dengan menghapus lalu mendaftar setelah debounce, yang bersama menghadirkan edit live tanpa downtime, tanpa crash, dan tanpa kontaminasihttps://docs-deserve.neabyte.com/diagrams/hot-reload-route-sequence.pngUrutan reload rute sebagaimana watcher menjalankannya, di mana Deno.watchFs mendeteksi perubahan lalu mendebounce 150ms, FastRouter.remove melepas pola lama, modul diimpor ulang dengan query timestamp untuk melewati cache, lalu divalidasi punya metode HTTP dan handler-nya didaftarkan sambil memancarkan route:reloaded, dan kegagalan apa pun di langkah itu malah memancarkan reload:error sehingga server tetap hidup dan rute lain tak terpengaruhhttps://docs-deserve.neabyte.com/core-concepts/multi-service2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/process-overview.pngOne Deno process running an API, Auth, and Web router, each on its own port with a client connecting to eachhttps://docs-deserve.neabyte.com/diagrams/router-isolation.pngEach router keeps its own FastRouter, middleware, and watcher in isolation, with the Web router also holding a DVE enginehttps://docs-deserve.neabyte.com/diagrams/shared-code-state.pngServices importing shared modules and communicating through an in-process session store, event bus, and cachehttps://docs-deserve.neabyte.com/diagrams/event-bus.pngThe API service emits an event to the EventBus, which notifies the Auth and Web serviceshttps://docs-deserve.neabyte.com/diagrams/per-service-middleware.pngEach service composes its own middleware chain before its routes: API runs CORS then BodyLimit, Auth runs SecHeaders, Web runs routes with DVEhttps://docs-deserve.neabyte.com/diagrams/observability.pngA single OTel middleware collects spans from every service and exports them to an OTel Collector, then on to Jaeger, Grafana, or Datadoghttps://docs-deserve.neabyte.com/diagrams/reverse-proxy.pngA reverse proxy such as Nginx or Caddy maps each hostname to a per-service port: api.example.com to 3001, auth.example.com to 3002, and example.com to 3003https://docs-deserve.neabyte.com/diagrams/scaling-out.pngExtracting services from a single process into separate API, Auth, and Web processeshttps://docs-deserve.neabyte.com/id/core-concepts/multi-service2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/process-overview.pngSatu proses Deno menjalankan router API, Auth, dan Web, masing-masing di port sendiri dengan satu klien terhubung ke tiap porthttps://docs-deserve.neabyte.com/diagrams/router-isolation.pngSetiap router punya FastRouter, middleware, dan watcher sendiri secara terisolasi, dengan router Web juga memegang DVE enginehttps://docs-deserve.neabyte.com/diagrams/shared-code-state.pngService mengimpor modul shared dan berkomunikasi lewat session store, event bus, dan cache dalam proseshttps://docs-deserve.neabyte.com/diagrams/event-bus.pngService API memancarkan event ke EventBus, yang memberi tahu service Auth dan Webhttps://docs-deserve.neabyte.com/diagrams/per-service-middleware.pngSetiap service menyusun rantai middleware sendiri sebelum rutenya: API menjalankan CORS lalu BodyLimit, Auth menjalankan SecHeaders, Web menjalankan rute dengan DVEhttps://docs-deserve.neabyte.com/diagrams/observability.pngSatu middleware OTel mengumpulkan span dari setiap service dan mengekspornya ke OTel Collector, lalu ke Jaeger, Grafana, atau Datadoghttps://docs-deserve.neabyte.com/diagrams/reverse-proxy.pngReverse proxy seperti Nginx atau Caddy memetakan tiap hostname ke port per-service: api.example.com ke 3001, auth.example.com ke 3002, dan example.com ke 3003https://docs-deserve.neabyte.com/diagrams/scaling-out.pngMengekstrak service dari satu proses menjadi proses API, Auth, dan Web yang terpisahhttps://docs-deserve.neabyte.com/core-concepts/philosophy2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/philosophy-beliefs-to-features.pngEach of the four core beliefs maps to a concrete feature you can reach today, where fewer moving parts leads to zero dependency, structure is the API leads to file-based routing, build on the platform leads to native HTTP and streams, and experience that scales leads to built for teamshttps://docs-deserve.neabyte.com/diagrams/philosophy-principle-web.pngAn abstract view of how the beliefs think as one mind, where a single root idea of staying as small as the problem feeds all four beliefs, the beliefs reinforce one another down the chain, and together they converge on the conclusion that simple is safe because less code means less that can go wronghttps://docs-deserve.neabyte.com/id/core-concepts/philosophy2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/philosophy-beliefs-to-features.pngMasing-masing dari empat keyakinan inti memetakan ke fitur konkret yang bisa dipakai hari ini, di mana lebih sedikit bagian bergerak menuju zero dependency, struktur adalah API menuju file-based routing, bangun di atas platform menuju HTTP dan stream native, dan pengalaman yang ikut tumbuh menuju dibangun untuk timhttps://docs-deserve.neabyte.com/diagrams/philosophy-principle-web.pngPandangan abstrak bagaimana keyakinan berpikir sebagai satu pikiran, di mana satu ide akar tetap sekecil masalah memberi makan keempat keyakinan, keyakinan saling menguatkan menyusuri rantai, dan bersama mereka menyatu pada kesimpulan bahwa sederhana itu aman sebab makin sedikit kode berarti makin sedikit yang bisa salahhttps://docs-deserve.neabyte.com/core-concepts/request-handling2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/core-concepts/request-handling2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/core-concepts/route-patterns2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/core-concepts/route-patterns2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/core-concepts/worker-pool2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/core-concepts/worker-pool2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/core-concepts/zero-dependency2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/zero-dep-supply-chain.pngA Node project pulls app code through the npm registry into hundreds of transitive dependencies where any update can be hostile, while a Deserve project uses only the Deno runtime and a few audited JSR moduleshttps://docs-deserve.neabyte.com/diagrams/zero-dep-runtime-primitives.pngDeserve draws request handling, file watching, security primitives, and permission flags straight from the built-in Deno runtime, so no npm package is neededhttps://docs-deserve.neabyte.com/diagrams/zero-dep-process-guard.pngA process sentinel interposes known termination calls, so self-targeted Deno.exit and process.exit are blocked and unhandled rejections are trapped while a kill aimed at another pid still passes through, keeping the process alive and emitting a process error eventhttps://docs-deserve.neabyte.com/diagrams/zero-dep-best-effort.pngWhat the guard protects against, self termination, uncaught faults, and denial of service, set beside what it does not do, since it is not a sandbox and untrusted code still runs, so it pairs with Deno permission flags and dependency reviewhttps://docs-deserve.neabyte.com/id/core-concepts/zero-dependency2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/zero-dep-supply-chain.pngProyek Node menarik kode aplikasi lewat registry npm ke ratusan dependensi transitif yang pembaruannya bisa berbahaya, sementara proyek Deserve hanya memakai runtime Deno dan sedikit modul JSR yang teraudithttps://docs-deserve.neabyte.com/diagrams/zero-dep-runtime-primitives.pngDeserve mengambil penanganan request, pemantauan berkas, primitif keamanan, dan flag izin langsung dari runtime Deno bawaan, jadi tidak butuh paket npmhttps://docs-deserve.neabyte.com/diagrams/zero-dep-process-guard.pngSebuah sentinel proses menyela panggilan terminasi yang dikenal, jadi Deno.exit dan process.exit ke diri sendiri diblokir dan unhandled rejection ditangkap sementara kill ke pid lain tetap lewat, menjaga proses tetap hidup dan memancarkan event process errorhttps://docs-deserve.neabyte.com/diagrams/zero-dep-best-effort.pngApa yang dilindungi guard, terminasi diri, fault tak tertangkap, dan denial of service, disandingkan dengan apa yang tidak dilakukannya, karena ini bukan sandbox dan kode tak tepercaya tetap berjalan, jadi ia berpasangan dengan flag izin Deno dan review dependensihttps://docs-deserve.neabyte.com/error-handling/default-behavior2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/default-error-behavior.pngWhen an error occurs, the request routes to a custom handler if router.catch is defined, otherwise to the default handler that returns JSON or HTML by Accept, then a single responsehttps://docs-deserve.neabyte.com/id/error-handling/default-behavior2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/default-error-behavior.pngSaat error terjadi, request diarahkan ke custom handler jika router.catch terdefinisi, jika tidak ke default handler yang mengembalikan JSON atau HTML sesuai Accept, lalu satu responsehttps://docs-deserve.neabyte.com/error-handling/defense-in-depth2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/defense-in-depth.pngFive layered error defenses: route handler try/catch, WrapMware labeled catch, router.catch custom handler, default handler with masked message, and the process guard that never crasheshttps://docs-deserve.neabyte.com/id/error-handling/defense-in-depth2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/defense-in-depth.pngLima lapis pertahanan error: try/catch route handler, WrapMware labeled catch, custom handler router.catch, default handler dengan pesan tersamar, dan process guard yang tidak pernah crashhttps://docs-deserve.neabyte.com/error-handling/object-details2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/error-handling/object-details2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/examples2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/examples2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/getting-started/built-for-teams2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/team-junior-ships.pngA junior ships on day one: creating routes/products/index.ts triggers the watcher's file-created event, the module is imported and its GET handler registered, and the route answers GET /products on the next request, with no restart and no shared config edit so there is no merge conflicthttps://docs-deserve.neabyte.com/diagrams/team-shared-rules.pngShared rules in one place: securityHeaders() registered with router.use(fn) reaches every route, while basicAuth() registered with router.use('/admin', fn) reaches only /admin/*, so one developer can own auth and another own logging without touching each other's route fileshttps://docs-deserve.neabyte.com/diagrams/team-many-hands.pngMany hands, one process: a single Deno process runs an API router owned by dev A on port 3001 and an Auth router owned by dev B on port 3002, each with its own routesDir and file watcher, so the two developers work in parallel without separate deployments or network gluehttps://docs-deserve.neabyte.com/id/getting-started/built-for-teams2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/team-junior-ships.pngJunior merilis di hari pertama: membuat routes/products/index.ts memicu event file-created dari watcher, modulnya diimpor dan handler GET-nya didaftarkan, lalu rute menjawab GET /products pada request berikutnya, tanpa restart dan tanpa edit config bersama sehingga tidak ada konflik mergehttps://docs-deserve.neabyte.com/diagrams/team-shared-rules.pngAturan bersama di satu tempat: securityHeaders() yang didaftarkan dengan router.use(fn) menjangkau setiap rute, sedangkan basicAuth() yang didaftarkan dengan router.use('/admin', fn) hanya menjangkau /admin/*, jadi satu developer bisa memegang auth dan yang lain memegang logging tanpa menyentuh berkas rute satu sama lainhttps://docs-deserve.neabyte.com/diagrams/team-many-hands.pngBanyak tangan, satu proses: satu proses Deno menjalankan router API milik dev A di port 3001 dan router Auth milik dev B di port 3002, masing-masing dengan routesDir dan file watcher sendiri, jadi kedua developer bekerja paralel tanpa deployment terpisah atau lem jaringanhttps://docs-deserve.neabyte.com/getting-started/installation2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/getting-started/installation2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/getting-started/quick-start2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/getting-started/quick-start2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/getting-started/routes-configuration2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/getting-started/routes-configuration2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/getting-started/server-configuration2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/getting-started/server-configuration2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/id/2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/basic-auth2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/basic-auth2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/body-limit2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/body-limit2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/cors2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/cors2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/csrf2026-06-09T01:34:32.000Zhttps://docs-deserve.neabyte.com/middleware/csrf2026-06-09T01:34:24.000Zhttps://docs-deserve.neabyte.com/id/middleware/global2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/middleware-global-registration.pngPendaftaran dan posisi Global Middleware: tiap router.use(fn) menambahkan entry path-kosong yang cocok untuk setiap request dan berjalan sebelum route matching, dalam urutan pendaftaranhttps://docs-deserve.neabyte.com/middleware/global2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/middleware-global-registration.pngGlobal Middleware registration and position: each router.use(fn) appends a path-empty entry that matches every request and runs before route matching, in registration orderhttps://docs-deserve.neabyte.com/diagrams/middleware-global-flow.pngGlobal Middleware per-request control flow: return await next() continues the chain, returning a Response stops and skips the handler, returning undefined is pass-through; throwing routes to router.catch or 500, and stalling triggers the requestTimeoutMs 503 guardhttps://docs-deserve.neabyte.com/id/middleware/ip2026-06-09T01:34:32.000Zhttps://docs-deserve.neabyte.com/middleware/ip2026-06-09T01:34:24.000Zhttps://docs-deserve.neabyte.com/id/middleware/observability/errors2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-process-fault.pngUnhandled rejection, uncaught error, dan terminasi diri yang diblokir masing-masing jadi event process:error yang membawa origin dan error-nya, jadi proses tetap berjalan tanpa downtime dan kesalahan tertangkap di listener router.on yang sama alih-alih hilang karena crashhttps://docs-deserve.neabyte.com/diagrams/obs-catch-vs-on.pngSatu request gagal menyebar ke dua hook independen, di mana router.catch membentuk Response yang diterima klien dengan status dan body terkontrol, dan router.on mencatat kegagalan yang sama ke log dan metrik tanpa memengaruhi balasanhttps://docs-deserve.neabyte.com/middleware/observability/errors2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-process-fault.pngUnhandled rejections, uncaught errors, and blocked self-termination each become a process:error event carrying its origin and error, so the process keeps running with no downtime and the fault is captured in the same router.on listener instead of being lost to a crashhttps://docs-deserve.neabyte.com/diagrams/obs-catch-vs-on.pngOne failed request fans out to two independent hooks, where router.catch shapes the Response the client receives with a controlled status and body, and router.on records the same failure into logs and metrics without affecting the replyhttps://docs-deserve.neabyte.com/id/middleware/observability/events2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-event-channel.pngEvent request bernilai external secara default tapi jadi internal ketika timeout, error framework, atau context yang hilang yang memicunya, sementara setiap kind non-request selalu internal, jadi merutekan berdasarkan field type menjaga lalu lintas klien normal tetap di luar kanal alert kesalahanhttps://docs-deserve.neabyte.com/middleware/observability/events2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-event-channel.pngA request event is external by default but becomes internal when a timeout, a framework error, or a missing context produced it, while every non-request kind is always internal, so routing on the type field keeps normal client traffic out of the fault alert channelhttps://docs-deserve.neabyte.com/id/middleware/observability/logging2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-request-lifecycle.pngSetiap request yang selesai memancarkan request:complete dengan metrik selaras OpenTelemetry, dan request dengan status 400 atau lebih juga memancarkan request:error yang membawa error asli, jadi satu listener router.on menyebarkan amplop yang sama ke satu baris access log, peringatan request lambat yang disaring berdasarkan durasi, dan laporan errorhttps://docs-deserve.neabyte.com/middleware/observability/logging2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-request-lifecycle.pngEvery finished request emits request:complete with OpenTelemetry-aligned metrics, and a request with status 400 or higher also emits request:error carrying the original error, so one router.on listener fans the same envelope into an access log line, a slow request warning filtered by duration, and an error reporthttps://docs-deserve.neabyte.com/id/middleware/observability/overview2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-single-bus.pngSinyal server, rute, view, request, dan proses semua menyatu ke satu event bus yang menyebarkan tiap event ke satu listener router.on, tempat kamu menyaring berdasarkan kind event, dan emit jadi no-op selama belum ada listener terdaftarhttps://docs-deserve.neabyte.com/middleware/observability/overview2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/obs-single-bus.pngServer, route, view, request, and process signals all funnel into a single event bus that fans every event to one router.on listener, where you filter by event kind, and the emit is a no-op while no listener is registeredhttps://docs-deserve.neabyte.com/id/middleware/route-specific2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/route-specific2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/middleware-route-matching.pngRoute-Specific prefix matching: router.use('/api', fn) matches /api exactly and /api/users on a boundary slash, but skips /apiv2 and /admin because they are not boundary matches of the prefixhttps://docs-deserve.neabyte.com/diagrams/middleware-route-chain.pngRoute-Specific execution for GET /api/users in one chain: the global logger runs, the /api auth runs on a prefix match, the /admin guard is skipped because it does not match without consuming a turn, the /api/users logger runs, then the route handler executes, all in registration orderhttps://docs-deserve.neabyte.com/id/middleware/security-headers2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/security-headers2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/session2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/session2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/middleware/websocket2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/middleware/websocket2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/recipes/file-upload2026-06-09T12:00:17.000Zhttps://docs-deserve.neabyte.com/recipes/file-upload2026-06-09T12:00:11.000Zhttps://docs-deserve.neabyte.com/id/recipes/streaming-data2026-06-09T12:00:17.000Zhttps://docs-deserve.neabyte.com/recipes/streaming-data2026-06-09T12:00:11.000Zhttps://docs-deserve.neabyte.com/id/rendering/2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/rendering/2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/rendering/performance2026-06-09T01:34:32.000Zhttps://docs-deserve.neabyte.com/rendering/performance2026-06-09T01:34:24.000Zhttps://docs-deserve.neabyte.com/id/rendering/streaming2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/stream-render-vs-blocking.pngBerdampingan, ctx.render membangun seluruh HTML jadi satu string lalu mengirim semuanya sekaligus sehingga klien menunggu, sementara ctx.streamRender mengompilasi di awal, mengembalikan ReadableStream, dan menulis tiap node saat diproduksi sehingga byte pertama keluar lebih cepathttps://docs-deserve.neabyte.com/diagrams/stream-render-pipeline.pngRute meng-await ctx.streamRender, engine meresolusi dan mengompilasi template, membuat TransformStream, mengembalikan sisi readable seketika sehingga header response terkirim, lalu merender ke sisi writable di latar belakang di mana kegagalan muncul sebagai event view errorhttps://docs-deserve.neabyte.com/diagrams/stream-render-chunks.pngStreaming melooping node template tingkat atas dan menulis tiap potongan yang diproduksi secara berurutan, jadi node teks ter-flush sendiri, tetapi blok each membangun semua barisnya jadi satu string dulu lalu ter-flush sebagai satu potongan, artinya granularitas streaming per node tingkat atas bukan per item loophttps://docs-deserve.neabyte.com/diagrams/stream-render-ttfb.pngPerbandingan time to first byte di mana render membuat klien menunggu selama seluruh halaman dibangun sehingga byte pertama datang terlambat, melawan streamRender yang mem-flush node pertama tepat setelah compile sehingga byte pertama datang lebih awal sementara potongan berikutnya terus berdatangan sampai stream ditutuphttps://docs-deserve.neabyte.com/rendering/streaming2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/stream-render-vs-blocking.pngSide by side, ctx.render builds the whole HTML into one string and sends it all at once so the client waits, while ctx.streamRender compiles up front, returns a ReadableStream, and writes each node as produced so the first bytes leave earlyhttps://docs-deserve.neabyte.com/diagrams/stream-render-pipeline.pngThe route awaits ctx.streamRender, the engine resolves and compiles the template, creates a TransformStream, returns the readable side at once so response headers go out, then renders into the writable side in the background where a failure surfaces as a view error eventhttps://docs-deserve.neabyte.com/diagrams/stream-render-chunks.pngStreaming loops the top-level template nodes and writes each produced chunk in order, so a text node flushes on its own, but an each block builds all its rows into one string first and then flushes as a single chunk, meaning the streaming granularity is per top-level node rather than per loop itemhttps://docs-deserve.neabyte.com/diagrams/stream-render-ttfb.pngA time to first byte comparison where render makes the client wait while the whole page is built so the first byte lands late, against streamRender which flushes the first node right after compile so the first byte lands early while later chunks keep arriving until the stream closeshttps://docs-deserve.neabyte.com/id/rendering/syntax2026-06-09T01:34:32.000Zhttps://docs-deserve.neabyte.com/rendering/syntax2026-06-09T01:34:24.000Zhttps://docs-deserve.neabyte.com/id/response/custom2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/custom2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/data2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/data2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/file2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/file2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/html2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/html2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/json2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/json2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/redirect2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/redirect2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/stream2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/stream2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/response/text2026-06-09T01:34:40.000Zhttps://docs-deserve.neabyte.com/response/text2026-06-09T01:34:14.000Zhttps://docs-deserve.neabyte.com/id/static-file/basic2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/static-url-to-file.pngMemanggil router.static dengan prefix garis miring static dan path titik garis miring public mendaftarkan pola garis miring static garis miring bintang bintang, lalu tiap request prefix garis miring static-nya dipotong dari ctx.pathname dan sisanya digabung di bawah public, jadi garis miring static memetakan ke public garis miring index titik html, garis miring static garis miring css garis miring style titik css memetakan ke public garis miring css garis miring style titik css, dan segmen apa pun yang diawali titik atau titik titik atau path yang lolos dari base ditolak dengan 404 sebelum pembacaan apa punhttps://docs-deserve.neabyte.com/static-file/basic2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/static-url-to-file.pngCalling router.static with the prefix slash static and path dot slash public registers the pattern slash static slash star star, then each request has its slash static prefix sliced off ctx.pathname and the remainder joined under public, so slash static maps to public slash index dot html, slash static slash css slash style dot css maps to public slash css slash style dot css, and any segment starting with a dot or dot dot or a path escaping the base is rejected with 404 before any readhttps://docs-deserve.neabyte.com/id/static-file/multiple2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/static-multiple-dirs.pngTiga panggilan static masing-masing mengikat satu prefix url ke foldernya sendiri dengan kebijakan cache sendiri, di mana garis miring admin menyajikan folder admin garis miring dist dengan etag aktif dan cache satu hari, garis miring uploads menyajikan folder uploads dengan etag nonaktif dan tanpa cache, dan garis miring docs menyajikan folder docs garis miring build dengan etag aktif dan cache satu jamhttps://docs-deserve.neabyte.com/diagrams/static-prefix-dispatch.pngSatu request memilih prefix static yang diawalinya, jadi GET garis miring uploads garis miring img garis miring a titik png cocok dengan pola garis miring uploads, prefiksnya dipotong, dan disajikan dari folder uploads dengan etag nonaktif dan tanpa cache, sementara tail yang sama pada GET garis miring docs garis miring img garis miring a titik png malah cocok dengan pola garis miring docs dan disajikan dari docs garis miring build dengan etag aktif dan cache satu jam, membuktikan prefix yang cocok menentukan folder sekaligus kebijakan cachehttps://docs-deserve.neabyte.com/static-file/multiple2026-06-09T05:07:47.000Zhttps://docs-deserve.neabyte.com/diagrams/static-multiple-dirs.pngThree static calls each bind one url prefix to its own folder with its own cache policy, where slash admin serves the admin slash dist folder with etag on and a one day cache, slash uploads serves the uploads folder with etag off and no cache, and slash docs serves the docs slash build folder with etag on and a one hour cachehttps://docs-deserve.neabyte.com/diagrams/static-prefix-dispatch.pngOne request picks the static prefix it starts with, so GET slash uploads slash img slash a dot png matches the slash uploads pattern, has its prefix sliced off, and is served from the uploads folder with that prefix etag off and no cache, while the same tail under GET slash docs slash img slash a dot png matches the slash docs pattern instead and is served from docs slash build with etag on and a one hour cache, proving the matched prefix decides both folder and cache policy