From a2d2a49cc29c7e193a74528355e84d54d60f1188 Mon Sep 17 00:00:00 2001 From: Mostafa Mahmoud Date: Mon, 14 Jul 2025 14:29:05 +0300 Subject: [PATCH] docs: adjust V8 RangeError message formatting Signed-off-by: Mostafa Mahmoud --- .../learn/asynchronous-work/event-loop-timers-and-nexttick.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/asynchronous-work/event-loop-timers-and-nexttick.md b/apps/site/pages/en/learn/asynchronous-work/event-loop-timers-and-nexttick.md index c5e4f107c5d22..91f0e4cfaacde 100644 --- a/apps/site/pages/en/learn/asynchronous-work/event-loop-timers-and-nexttick.md +++ b/apps/site/pages/en/learn/asynchronous-work/event-loop-timers-and-nexttick.md @@ -331,7 +331,7 @@ callback _after_ the rest of the user's code and _before_ the event loop is allowed to proceed. To achieve this, the JS call stack is allowed to unwind then immediately execute the provided callback which allows a person to make recursive calls to `process.nextTick()` without reaching a -`RangeError: Maximum call stack size exceeded from v8`. +`RangeError: Maximum call stack size exceeded` from v8. This philosophy can lead to some potentially problematic situations. Take this snippet for example: