From 98918110a14b190ede5e788c27ed603151227cef Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Tue, 8 Dec 2020 10:49:15 -0800 Subject: [PATCH] doc: edit addon text about event loop blocking PR-URL: https://github.com/nodejs/node/pull/36448 Reviewed-By: Luigi Pinca Reviewed-By: James M Snell Reviewed-By: Anna Henningsen Reviewed-By: Shelley Vohr --- doc/api/addons.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/addons.md b/doc/api/addons.md index 9f7e8900989d04..4df723c74ffd61 100644 --- a/doc/api/addons.md +++ b/doc/api/addons.md @@ -28,10 +28,10 @@ involving knowledge of several components and APIs: as interacting with the filesystem, sockets, timers, and system events. libuv also provides a threading abstraction similar to POSIX threads for more sophisticated asynchronous addons that need to move beyond the - standard event loop. Addon authors are encouraged to think about how to + standard event loop. Addon authors should avoid blocking the event loop with I/O or other time-intensive tasks by - off-loading work via libuv to non-blocking system operations, worker threads - or a custom use of libuv's threads. + offloading work via libuv to non-blocking system operations, worker threads, + or a custom use of libuv threads. * Internal Node.js libraries. Node.js itself exports C++ APIs that addons can use, the most important of which is the `node::ObjectWrap` class.