denoland-deno/cli/tests/node_compat/runner.ts

// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.
import "./polyfill_globals.js";
import { createRequire } from "node:module";
const file = Deno.args[0];
if (!file) {
  throw new Error("No file provided");
}
createRequire(import.meta.url)(file);
test: add node compat tests (#17805) 2023-02-17 23:58:52 +09:00			`// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.`
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			`import "./polyfill_globals.js";`
test: add node compat tests (#17805) 2023-02-17 23:58:52 +09:00			`import { createRequire } from "node:module";`
			`const file = Deno.args[0];`
			`if (!file) {`
			`throw new Error("No file provided");`
			`}`
			`createRequire(import.meta.url)(file);`
No results found.