electron/atom/common/lib/init.js

48 lines
1.6 KiB
JavaScript
Raw Normal View History

2016-01-14 22:11:50 +00:00
const path = require('path');
const timers = require('timers');
const Module = require('module');
2016-01-12 02:40:23 +00:00
process.atomBinding = function(name) {
try {
return process.binding("atom_" + process.type + "_" + name);
} catch (error) {
if (/No such module/.test(e.message)) {
return process.binding("atom_common_" + name);
}
}
};
if (!process.env.ELECTRON_HIDE_INTERNAL_MODULES) {
2016-01-14 18:35:29 +00:00
// Add common/api/lib to module search paths.
2016-01-12 02:40:23 +00:00
Module.globalPaths.push(path.resolve(__dirname, '..', 'api', 'lib'));
}
2016-01-14 18:44:21 +00:00
// setImmediate and process.nextTick makes use of uv_check and uv_prepare to
// run the callbacks, however since we only run uv loop on requests, the
// callbacks wouldn't be called until something else activated the uv loop,
// which would delay the callbacks for arbitrary long time. So we should
// initiatively activate the uv loop once setImmediate and process.nextTick is
// called.
2016-01-14 22:11:50 +00:00
var wrapWithActivateUvLoop = function(func) {
2016-01-12 02:40:23 +00:00
return function() {
process.activateUvLoop();
return func.apply(this, arguments);
};
};
process.nextTick = wrapWithActivateUvLoop(process.nextTick);
global.setImmediate = wrapWithActivateUvLoop(timers.setImmediate);
global.clearImmediate = timers.clearImmediate;
if (process.type === 'browser') {
2016-01-14 18:44:21 +00:00
// setTimeout needs to update the polling timeout of the event loop, when
// called under Chromium's event loop the node's event loop won't get a chance
// to update the timeout, so we have to force the node's event loop to
// recalculate the timeout in browser process.
2016-01-12 02:40:23 +00:00
global.setTimeout = wrapWithActivateUvLoop(timers.setTimeout);
global.setInterval = wrapWithActivateUvLoop(timers.setInterval);
}