denoland-deno/tests/specs/npm/compare_globals/main.out

[UNORDERED_START]
Download http://localhost:4260/@types%2fnode
Download http://localhost:4260/undici-types
Download http://localhost:4260/@denotest%2fglobals
[UNORDERED_END]
[UNORDERED_START]
Download http://localhost:4260/@denotest/globals/1.0.0.tgz
Download http://localhost:4260/@types/node/node-22.5.4.tgz
Download http://localhost:4260/undici-types/undici-types-6.19.8.tgz
[UNORDERED_END]
Check file:///[WILDCARD]/main.ts
true
true
[]
process equals process true
setTimeout 1 false
setTimeout 2 function
setTimeout 3 function
setTimeout 4 function
setTimeout 5 undefined
window 1 false
window 2 false
false
false
self 1 true
self 2 true
false
false
bar
bar
true
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]`
fix(npm): ensure scoped package name is encoded in URLs (#26390) Fixes https://github.com/denoland/deno/issues/26385 2024-10-18 14:38:57 -04:00			`Download http://localhost:4260/@types%2fnode`
feat: TypeScript 5.6 and `npm:@types/node@22` (#25614) 2024-09-14 06:58:47 -04:00			`Download http://localhost:4260/undici-types`
fix(npm): ensure scoped package name is encoded in URLs (#26390) Fixes https://github.com/denoland/deno/issues/26385 2024-10-18 14:38:57 -04:00			`Download http://localhost:4260/@denotest%2fglobals`
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`
feat: TypeScript 5.6 and `npm:@types/node@22` (#25614) 2024-09-14 06:58:47 -04:00			`Download http://localhost:4260/@types/node/node-22.5.4.tgz`
			`Download http://localhost:4260/undici-types/undici-types-6.19.8.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]`
fix(check): expose more globals from @types/node (#26603) Extracted out of https://github.com/denoland/deno/pull/26558 Closes https://github.com/denoland/deno/issues/26578 2024-10-28 17:43:41 -04:00			`Check file:///[WILDCARD]/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			`[]`
fix(check): expose more globals from @types/node (#26603) Extracted out of https://github.com/denoland/deno/pull/26558 Closes https://github.com/denoland/deno/issues/26578 2024-10-28 17:43:41 -04:00			`process equals process true`
BREAKING: `DENO_FUTURE=1` by default, or welcome to Deno 2.0 (#25213) This commit effectively turns Deno into Deno 2.0. This is done by forcing `DENO_FUTURE=1` env var, that was available in the past few months to try Deno 2 changes. This commit contains several breaking changes scheduled for Deno 2: - all deprecated JavaScript APIs are not available any more, mostly `Deno.` APIs - `window` global is removed - FFI, WebGPU and FS APIs are now stable and don't require `--unstable-` flags - import assertions are no longer supported - "bring your own node modules" is enabled by default This is the first commit in a series that are scheduled before the Deno 2 release. Follow up work is tracked in https://github.com/denoland/deno/issues/25241. --------- Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com> Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com> Co-authored-by: Nathan Whitaker <nathan@deno.com> 2024-08-30 13:58:58 -04:00			`setTimeout 1 false`
			`setTimeout 2 function`
			`setTimeout 3 function`
			`setTimeout 4 function`
			`setTimeout 5 undefined`
			`window 1 false`
			`window 2 false`
fix(ext/node): do not expose `self` global in node (#24637) closes #23727 2024-07-18 23:37:08 -04:00			`false`
			`false`
BREAKING: `DENO_FUTURE=1` by default, or welcome to Deno 2.0 (#25213) This commit effectively turns Deno into Deno 2.0. This is done by forcing `DENO_FUTURE=1` env var, that was available in the past few months to try Deno 2 changes. This commit contains several breaking changes scheduled for Deno 2: - all deprecated JavaScript APIs are not available any more, mostly `Deno.` APIs - `window` global is removed - FFI, WebGPU and FS APIs are now stable and don't require `--unstable-` flags - import assertions are no longer supported - "bring your own node modules" is enabled by default This is the first commit in a series that are scheduled before the Deno 2 release. Follow up work is tracked in https://github.com/denoland/deno/issues/25241. --------- Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com> Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com> Co-authored-by: Nathan Whitaker <nathan@deno.com> 2024-08-30 13:58:58 -04:00			`self 1 true`
			`self 2 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			`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`