info/developer-roadmap
1
0
Fork 0
mirror of https://github.com/kamranahmedse/developer-roadmap.git synced 2025-08-21 16:41:24 +02:00
Code Issues Releases Wiki Activity

Add content for error handling in node.js (#2492)

Browse Source
This commit is contained in:
Arya Singh
2022-10-21 23:07:06 +05:30
committed by GitHub
parent 1ae152ead1
commit 1f3b2a280d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/roadmaps/107-nodejs/content/103-nodejs-error-handling/102-uncaught-exceptions.md
View File

@@ -2,7 +2,7 @@
When a JavaScript error is not properly handled, an uncaughtException is emitted. These suggest the programmer has made an error, and they should be treated with the utmost priority. When a JavaScript error is not properly handled, an uncaughtException is emitted. These suggest the programmer has made an error, and they should be treated with the utmost priority.
The correct use of 'uncaughtException' is to perform synchronous cleanup of allocated resources (e.g. file descriptors, handles, etc) before shutting down the process. It is not safe to resume normal operation after 'uncaughtException'. The correct use of `uncaughtException` is to perform synchronous cleanup of allocated resources (e.g. file descriptors, handles, etc) before shutting down the process. It is not safe to resume normal operation after `uncaughtException` because system becomes corrupted. The best way is to let the application crash, log the error and then restart the process automatically using nodemon or pm2.
<ResourceGroupTitle>Free Content</ResourceGroupTitle> <ResourceGroupTitle>Free Content</ResourceGroupTitle>
<BadgeLink colorScheme='blue' badgeText='Official Website' href='https://nodejs.org/api/process.html#event-uncaughtexception'>Official Website</BadgeLink> <BadgeLink colorScheme='blue' badgeText='Official Website' href='https://nodejs.org/api/process.html#event-uncaughtexception'>Official Website</BadgeLink>