209 } catch (cerr) {
210 console.error(cerr);
211 }
212 process.exit(1);213})
214const splchecker = new SpellChecker(new SpellCfg({ ignoreCase: false, languages: ['en-us'] }));
215splchecker.addProviderByConfig({ name: 'hunspell' });186 process.exit(0);
187 } catch (err) {
188 console.error(err);
189 process.exit(1);190 }
191})
192process.on("uncaughtException", async (err) => {183 embeds: [mbed],
184 });
185 }
186 process.exit(0);187 } catch (err) {
188 console.error(err);
189 process.exit(1); 9 readline.question("What's the URL/path of the avatar? ", url => {
10 bot.user.setAvatar(url).then(() => {
11 console.log("All done!")
12 process.exit(0)13 }).catch(e => { throw e })
14 })
15})The process.exit() method in Node.js is used to immediately stop the Node.js process and exit. This is a dangerous operation because it can occur in any method at any point in time, potentially stopping a Node.js application completely when an error occurs. For example:
if (somethingBadHappened) {
console.error("Something bad happened!");
process.exit(1);
}
This code could appear in any module and will stop the entire application when somethingBadHappened is truthy. This doesn't give the application any chance to respond to the error. It's usually better to throw an error and allow the application to handle it appropriately:
if (somethingBadHappened) {
throw new Error("Something bad happened!");
}
By throwing an error in this way, other parts of the application have an opportunity to handle the error rather than stopping the application altogether. If the error bubbles all the way up to the process without being handled, then the process will exit and a non-zero exit code will returned, so the end result is the same.
If you are using process.exit() only for specifying the exit code, you can set process.exitCode (introduced in Node.js 0.11.8) instead.
Bad Practice
process.exit(1);
process.exit(0);
Recommended
Process.exit();
var exit = process.exit;