1 day ago

This is the coolest thing about the Unsandboxed extension repo.


Ok so TurboWarp extensions are wrapped in IIFEs and load using "Scratch.extensions.register" which is annoying if you're me because I wanted the Unsandboxed extension specification to export extension classes as modules.

However, I also wanted to remain as close to TurboWarp as possible, so the TW extension docs would be interchangeable.

What do I do? Do both lmao.

Webpack compiles all extension code wrapped in IIFEs to export the extension class as a module, so devs don't have to change anything about how they write extensions. As far as they're concerned, its the same as TurboWarp.

Who says I can't have my cake and eat it too lmao.

1
Unsandboxed Extensions
12


0 comments

Loading...

Next up

im making even more changes to our renderer, as well as some internal fixes for things like connections.

Other mods are fun. "Why fix compiler when can remove errors from showing up at all?"

I genuinely wish I could be this chill when adding shit. It would be 10x more fun.

Also LibreKitten is neat, go see what they're doing

Non-deprecated "addons" will be contained within the same menu as the other settings.

Reminder that some addons will be removed as they are reworked to be built-in additions to Unsandboxed.

Our extensions will be loaded and treated as built-in extensions from the VM, but from a separate repository. No URLs, just raw Unsandboxed extensions. In the true spirit of our name, and without the VM clutter.

A minor update has been released for Unsandboxed.

Full changelog is in the article.

im COOKING