Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for loading custom extensions in compiled projects #31

Closed
MikeDev101 opened this issue May 7, 2021 · 1 comment
Closed
Labels
bug Something isn't working enhancement New feature or request

Comments

@MikeDev101
Copy link

Projects that use experimental extensions will throw an error stating SecurityError: Failed to construct 'Worker': Script at (file:///) cannot be accessed from origin 'null'. Since the packager is a modified version of TurboWarp, how hard would it be to implement experimental extension support?

@GarboMuffin GarboMuffin added bug Something isn't working enhancement New feature or request labels May 8, 2021
@GarboMuffin
Copy link
Member

GarboMuffin commented May 22, 2021

Using the new custom JS feature, you can do, eg.

vm.extensionManager.loadExtensionURL("https://extensions.turbowarp.org/fetch.js")

and it will load your extension

(there were also other fixes to make custom extensions actually work in the packager)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants