denoland-deno/ext/node/polyfills/00_globals.js

// Copyright 2018-2025 the Deno authors. MIT license.

// deno-lint-ignore-file

export const denoGlobals = globalThis.__bootstrap.ext_node_denoGlobals;
export const nodeGlobals = globalThis.__bootstrap.ext_node_nodeGlobals;
chore: Happy New Year 2025 (#27509) 2025-01-01 04:12:39 +09:00			`// Copyright 2018-2025 the Deno authors. MIT license.`
feat(unstable): initial support for npm specifiers (#15484) Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> 2022-08-20 11:31:33 -04:00
			`// deno-lint-ignore-file`

feat(ext/node): properly segregate node globals (#19307) 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> 2023-07-19 10:30:04 +02:00			`export const denoGlobals = globalThis.__bootstrap.ext_node_denoGlobals;`
			`export const nodeGlobals = globalThis.__bootstrap.ext_node_nodeGlobals;`