mirror of
https://github.com/denoland/deno.git
synced 2024-12-04 17:18:23 -05:00
e511022c74
Code run within Deno-mode and Node-mode should have access to a slightly different set of globals. Previously this was done through a compile time code-transform for Node-mode, but this is not ideal and has many edge cases, for example Node's globalThis having a different identity than Deno's globalThis. This commit makes the `globalThis` of the entire runtime a semi-proxy. This proxy returns a different set of globals depending on the caller's mode. This is not a full proxy, because it is shadowed by "real" properties on globalThis. This is done to avoid the overhead of a full proxy for all globalThis operations. The globals between Deno-mode and Node-mode are now properly segregated. This means that code running in Deno-mode will not have access to Node's globals, and vice versa. Deleting a managed global in Deno-mode will NOT delete the corresponding global in Node-mode, and vice versa. --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> Co-authored-by: Aapo Alasuutari <aapo.alasuutari@gmail.com>
25 lines
No EOL
634 B
JavaScript
25 lines
No EOL
634 B
JavaScript
exports.globalThis = globalThis;
|
|
exports.global = global;
|
|
exports.process = process;
|
|
|
|
exports.deleteSetTimeout = function () {
|
|
delete globalThis.setTimeout;
|
|
};
|
|
|
|
exports.getSetTimeout = function () {
|
|
return globalThis.setTimeout;
|
|
};
|
|
|
|
exports.checkProcessGlobal = function () {
|
|
console.log("process" in globalThis);
|
|
console.log(Object.getOwnPropertyDescriptor(globalThis, "process") !== undefined);
|
|
};
|
|
|
|
exports.checkWindowGlobal = function () {
|
|
console.log("window" in globalThis);
|
|
console.log(Object.getOwnPropertyDescriptor(globalThis, "window") !== undefined);
|
|
}
|
|
|
|
exports.getFoo = function () {
|
|
return globalThis.foo;
|
|
} |