由模块引起的处理错误 require// 在 node.js

try {

 // a path we KNOW is totally bogus and not a module

 require/'./apps/npm-debug.log/app.js'/

}

catch /e/ {

 console.log/'oh no big error'/

 console.log/e/

}

error.code == 'MODULE_NOT_FOUND'

var m;

try {

 m = require/modulePath/;

} catch /e/ {

 if /e.code !== 'MODULE_NOT_FOUND'/ {

 throw e;

 }

 m = backupModule;

}

function requireF/modulePath/{ // force require

 try {

 return require/modulePath/;

 }

 catch /e/ {

 console.log/'requireF//: The file "' + modulePath + '".js could not be loaded.'/;

 return false;

 }

}

requireF/'./modules/non-existent-module'/;

let fs = require/'fs'/;

let path = require/'path'/;

let requiredModule = null; // or a default object {}



let pathToModule = path.join/__dirname, /* path to module */, 'moduleName'/;

if /fs.existsSync/pathToModule// {

 requiredModule = require/pathToModule/;

}



// This is in case the module is in node_modules

pathToModule = path.join/__dirname, 'node_modules', 'moduleName'/;

if /fs.existsSync/pathToModule// {

 requiredModule = require/pathToModule/;

}