deno_core Extension with Global Access
Is there a way to make a Deno Extension be accessed by
Extension.op()Deno.core.ops.op()
DDoes this work?
OOf course that does work, but that'd require asking everyone to add that, I'm looking for a way to make it so whenever is run, it'll just work.
Bcurrently it's not possible OOTB, you need to handle it yourself
OSo how do extensions like and have their stuff globally?
OI'm willing to add a JS file to the extension.
Bthe global scope is assembled in a file called that is executed after all extensions have been loaded and added their relevant stuff to different namespaces
OSo is there no way to implement a similar functionality as that into my own project without forking?
Byou certainly can, which crates do you use? do you use crate?
OYes, runtime.
Bif you use it will be harder right now - @crowlkats and I are working on a PR that will make it much easier (https://github.com/denoland/deno/pull/16597) that will allows to extend global scope as you see fit
Ball in all you should still be able to assign whatever you want to after all JS code from crates executes
OWhat's the goal for that pr? (If any)
Bto allow creating V8 snapshots from existing V8 snapshots
Bso you can extend what's already in and change it as you see fit
Bmainly useful for a windowing project Leo is working on
OAround how long should I expect to wait for that
Ba week probably
OSo next patch?
OAlright. I appreciate all of this work. Thanks for the knowledge.
Byes, next patch release
O@.bartlomieju i see it was released, how would i properly add to the globalThis?
B@crowlkats can you give a quick rundown?
Ca live example of this is the cli in the deno repo.
first is the build script:
first off you need to define a path for the snapshot and path for where you have your js files
https://github.com/denoland/deno/blob/main/cli/build.rs#L460-L463
and then the actual snapshot creation
https://github.com/denoland/deno/blob/main/cli/build.rs#L271-L317
then you need to get the snapshot during execution https://github.com/denoland/deno/blob/main/cli/js.rs and pass it to your 's .
then, in a js file in the folder you defined as js folder you do whatever you need to do, inside the usual iief; at the end of the iief you add to the global scope whatever you want with
first is the build script:
first off you need to define a path for the snapshot and path for where you have your js files
https://github.com/denoland/deno/blob/main/cli/build.rs#L460-L463
and then the actual snapshot creation
https://github.com/denoland/deno/blob/main/cli/build.rs#L271-L317
then you need to get the snapshot during execution https://github.com/denoland/deno/blob/main/cli/js.rs and pass it to your 's .
then, in a js file in the folder you defined as js folder you do whatever you need to do, inside the usual iief; at the end of the iief you add to the global scope whatever you want with
Ocan this be done with extensions instead of everything in the build.rs? I dont exactly follow correctly
CI am not sure I understand
OHow would I do this with an extension? Do I have to put everything in the js folder, or can I integrate extensions into this as well?
Cah, at the time it wasnt possible, but now it is
Ci can write you up how in a bit
OCould I have this please?
Cmy bad, forgot about it. will do it now
OThank you 
Csadly there is no live example.
first instead of doing https://github.com/denoland/deno/blob/main/cli/build.rs#L474-L475, just use a vec with in it.
Then, in there is a new field called ; to that you pass a vec of extensions you want to use to add additional js files.
first instead of doing https://github.com/denoland/deno/blob/main/cli/build.rs#L474-L475, just use a vec with in it.
Then, in there is a new field called ; to that you pass a vec of extensions you want to use to add additional js files.
Cthat should be all
OIf I want all the default extensions in the cli, would I have to add those myself?
O hmm
OO@crowlkats it errors out if you leave extensions as a vec. Is this intended?
OIt seems you have to include every single extension the runtime uses for a successful build. Seems kinda frustrating, and would make maintaining the list frustrating.
Cunsure how we could improve that really
C@.bartlomieju thoughts?
OI mean it wouldn't be challenging to add all the extensions to my project, it's just maintaining that list would be frustrating.
OOBwell we had this one idea, that each would specify its name in the builder and then we could add and panic if one of the extensions hasn't been yet registered
Bthat would make debugging problems much easier in such case
Cah yea, though that still seems not perfect
Cmaybe make a function that returns a vec of extensions in deno_runtime?
Bthat's also an option
OThat was the idea I had, but unless you want to do that in deno_core or made a new package for that, you couldn't access it in the runtime build script
Cyea thats the one problem with it...