mirror of
https://github.com/denoland/deno.git
synced 2024-12-25 16:49:18 -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>
23 lines
423 B
Text
23 lines
423 B
Text
Download http://localhost:4545/npm/registry/@types/node
|
|
Download http://localhost:4545/npm/registry/@denotest/globals
|
|
Download http://localhost:4545/npm/registry/@denotest/globals/1.0.0.tgz
|
|
Download http://localhost:4545/npm/registry/@types/node/node-18.8.2.tgz
|
|
Check file:///[WILDCARD]/npm/compare_globals/main.ts
|
|
true
|
|
true
|
|
[]
|
|
false
|
|
function
|
|
function
|
|
function
|
|
undefined
|
|
false
|
|
false
|
|
true
|
|
true
|
|
true
|
|
true
|
|
false
|
|
false
|
|
bar
|
|
bar
|