foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-22 15:06:54 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/tests/testdata/npm/compare_globals/main.out

33 lines
468 B
Text
Raw Normal View History

refactor: remove `DENO_UNSTABLE_NPM_SYNC_DOWNLOAD` and custom sync functionality (#20504) https://github.com/denoland/deno/pull/20488 enables us to remove this functionality. This is better because our test suite is now not testing a separate code path.
2023-09-14 13:51:28 -04:00
[UNORDERED_START]
chore: fix flaky net_listen_allow_localhost_4555 (#23726) Moves the test npm registry server port from `4558` to `426x`
2024-05-07 13:21:56 -04:00
Download http://localhost:4260/@types/node
Download http://localhost:4260/@denotest/globals
refactor: remove `DENO_UNSTABLE_NPM_SYNC_DOWNLOAD` and custom sync functionality (#20504) https://github.com/denoland/deno/pull/20488 enables us to remove this functionality. This is better because our test suite is now not testing a separate code path.
2023-09-14 13:51:28 -04:00
[UNORDERED_END]
[UNORDERED_START]
chore: fix flaky net_listen_allow_localhost_4555 (#23726) Moves the test npm registry server port from `4558` to `426x`
2024-05-07 13:21:56 -04:00
Download http://localhost:4260/@denotest/globals/1.0.0.tgz
Download http://localhost:4260/@types/node/node-18.16.19.tgz
refactor: remove `DENO_UNSTABLE_NPM_SYNC_DOWNLOAD` and custom sync functionality (#20504) https://github.com/denoland/deno/pull/20488 enables us to remove this functionality. This is better because our test suite is now not testing a separate code path.
2023-09-14 13:51:28 -04:00
[UNORDERED_END]
feat(unstable/npm): initial type checking of npm specifiers (#16332)
2022-10-21 11:20:18 -04:00
Check file:///[WILDCARD]/npm/compare_globals/main.ts
fix(ext/node): fix global in node env (#15622)
2022-08-26 10:39:05 -04:00
true
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 04:30:04 -04:00
true
feat(unstable/npm): initial type checking of npm specifiers (#16332)
2022-10-21 11:20:18 -04:00
[]
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 04:30:04 -04:00
false
function
function
function
fix: use static Reflect methods in nodeGlobalThis proxy (#17696) Co-authored-by: David Sherret <dsherret@gmail.com>
2023-02-08 19:11:12 -05:00
undefined
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 04:30:04 -04:00
false
false
true
true
true
true
fix(ext/node): do not expose `self` global in node (#24637) closes #23727
2024-07-18 23:37:08 -04:00
true
true
false
false
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 04:30:04 -04:00
false
false
bar
bar
fix(ext/node): include non-enumerable keys in `Reflect.ownKeys(globalThis)` (#21485) Closes #21484.
2023-12-07 11:04:44 -05:00
true
Copy permalink