Deno core is leaking into user script

[CGQAQ]

Version: Deno 2.1.7

Users can access deno core through Deno[Deno.internal].core, I think it's not intentional

Details

~ deno
Deno 2.1.7
exit using ctrl+d, ctrl+c, or close()
REPL is running with all permissions allowed.
To specify permissions, run `deno repl` with allow flags.
> Deno[Deno.internal].core.isTypedArray
[Function: isTypedArray]
> Deno[Deno.internal].core.getPromiseDetails
[Function: getPromiseDetails]
> Deno[Deno.internal].core.getPromiseDetails(Promise.resolve(true))
[ 1, true ]
> Deno[Deno.internal].core.getPromiseDetails(Promise.reject(true))
[ 2, true ]
Uncaught undefined
> let a = {}
undefined
> let b = new Proxy(a, {})
undefined
> Deno[Deno.internal].core.getProxyDetails(b)
[ {}, {} ]
> a.a = "hello"
"hello"
> Deno[Deno.internal].core.getProxyDetails(b)
[ { a: "hello" }, {} ]

[bartlomieju]

This is on purpose and by design. Most of "dangerous" ops are not accessible that way and the remaining APIs are harmless.