From 862a2fb6ed8766138b95ef44056bebb554b0fb0e Mon Sep 17 00:00:00 2001
From: Willem-Jaap <67187467+Willem-Jaap@users.noreply.github.com>
Date: Tue, 12 May 2026 14:28:43 +0200
Subject: [PATCH 1/4] fix: fix typo in jit compiler docs
---
docs/internal/jit-compiler.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/internal/jit-compiler.md b/docs/internal/jit-compiler.md
index 64ed9763..c00c1b90 100644
--- a/docs/internal/jit-compiler.md
+++ b/docs/internal/jit-compiler.md
@@ -27,7 +27,7 @@ Elysia is fast and will likely remain *one of the fastest web frameworks for Jav
-Elysia speed is not only acheived by optimization for specific runtime eg. Bun native features like `Bun.serve.routes`. But also the way Elysia handles route registration and request handling.
+Elysia speed is not only achieved by optimization for specific runtime eg. Bun native features like `Bun.serve.routes`. But also the way Elysia handles route registration and request handling.
Elysia has an **JIT "compiler"** embedded within its core since [Elysia 0.4](/blog/elysia-04) (30 Mar 2023) at (*src/compose.ts*) using `new Function(...)` or also known as `eval(...)`.
From 6728e05156dad834ee25525a10e4264e5cad2e89 Mon Sep 17 00:00:00 2001
From: Willem-Jaap <67187467+Willem-Jaap@users.noreply.github.com>
Date: Tue, 12 May 2026 14:51:40 +0200
Subject: [PATCH 2/4] update grammar
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
---
docs/internal/jit-compiler.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/internal/jit-compiler.md b/docs/internal/jit-compiler.md
index c00c1b90..f3752da8 100644
--- a/docs/internal/jit-compiler.md
+++ b/docs/internal/jit-compiler.md
@@ -27,7 +27,7 @@ Elysia is fast and will likely remain *one of the fastest web frameworks for Jav
-Elysia speed is not only achieved by optimization for specific runtime eg. Bun native features like `Bun.serve.routes`. But also the way Elysia handles route registration and request handling.
+Elysia speed is not only achieved by optimization for specific runtime eg. Bun native features like `Bun.serve.routes`, but also by the way Elysia handles route registration and request handling.
Elysia has an **JIT "compiler"** embedded within its core since [Elysia 0.4](/blog/elysia-04) (30 Mar 2023) at (*src/compose.ts*) using `new Function(...)` or also known as `eval(...)`.
From 53cb11ccc666fecb0b504a34af9bc34b5f8bbcc9 Mon Sep 17 00:00:00 2001
From: Chiboy
Date: Thu, 9 Jul 2026 07:46:13 +0100
Subject: [PATCH 3/4] Fix typos in jit-compiler.md documentation
Corrected typos in the JIT compiler documentation regarding request overhead and optimization descriptions.
---
docs/internal/jit-compiler.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/internal/jit-compiler.md b/docs/internal/jit-compiler.md
index f3752da8..be250b4f 100644
--- a/docs/internal/jit-compiler.md
+++ b/docs/internal/jit-compiler.md
@@ -147,7 +147,7 @@ Elysia JIT *"compiler"* is designed for peak performance in mind. However, the d
### Initial Request Overhead
The first time a request is made to a specific route, Elysia needs to analyze the route handler code and generate the optimized code.
-This process is relatively **very fast** and usually takes < 0.005ms per route in most cases on a modern CPU and happend only **once per route**. But it is still an overhead.
+This process is relatively **very fast** and usually takes < 0.005ms per route in most cases on a modern CPU and happens only **once per route**. But it is still an overhead.
@@ -189,7 +189,7 @@ Although, it's not recommended because there are some features missing without J
## Afterword
-With all of these *overkills* optimization, Elysia manages to have *almost* zero overhead and the only limiting factor is the speed of the underlying JavaScript engine itself.
+While all of this *overkills* optimization, Elysia manages to have *almost* zero overhead and the only limiting factor is the speed of the underlying JavaScript engine itself.
Despite the maintainability challenges, the trade-offs made by Elysia's JIT "compiler" are worth it for the significant performance gains it provides and aligns with our goal to provide a fast foundation for building high-performance server.
From 715f71b23a3464bca5138d61ddb08444c86fe5dd Mon Sep 17 00:00:00 2001
From: Willem-Jaap <67187467+Willem-Jaap@users.noreply.github.com>
Date: Thu, 9 Jul 2026 12:01:23 +0200
Subject: [PATCH 4/4] docs: fix wording
---
docs/internal/jit-compiler.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/internal/jit-compiler.md b/docs/internal/jit-compiler.md
index be250b4f..e91fb8eb 100644
--- a/docs/internal/jit-compiler.md
+++ b/docs/internal/jit-compiler.md
@@ -189,7 +189,7 @@ Although, it's not recommended because there are some features missing without J
## Afterword
-While all of this *overkills* optimization, Elysia manages to have *almost* zero overhead and the only limiting factor is the speed of the underlying JavaScript engine itself.
+With all of this *overkill* optimization, Elysia manages to have *almost* zero overhead and the only limiting factor is the speed of the underlying JavaScript engine itself.
Despite the maintainability challenges, the trade-offs made by Elysia's JIT "compiler" are worth it for the significant performance gains it provides and aligns with our goal to provide a fast foundation for building high-performance server.