Here is a tip to test ScratchX and see what works and what doesn't as well as debugging without having to add, commit, push to GitHub and wait for GitHub pages to update.
All you need to do is edit the extension locally, and then to test it open ScratchX and click ‘Open Editor’.
Then open your JavaScript console and copy the extension into the console and press enter/return.
To make changes simply type ‘ScratchExtensions.unregister(“extension name here’)” into the console and press enter. It needs to be spelt correctly and is case sensitive (uppercase and lowercase need to match with the extension). Then make changes and copy and paste it again. This should save time if you are making little changes and seeing what works. Ta-da!

What about right clicking the load extension button to load from file?

I coded up a local server in Java to serve the extension fresh from my file system with every request(with no-cache headers to be safe), and a block that I can click to reload the extension in ScratchX.

Then, all I do to load the extension with a ScratchX link pointing to localhost, which gets auto completed by my browser. Then I just edit and save the extension, then click the reload block. No page reloads, no console, reloading takes like a tenth of a second, and any tests I set up in ScratchX stay there.

Znapi wrote:

I coded up a local server in Java to serve the extension fresh from my file system with every request(with no-cache headers to be safe), and a block that I can click to reload the extension in ScratchX.

Then, all I do to load the extension with a ScratchX link pointing to localhost, which gets auto completed by my browser. Then I just edit and save the extension, then click the reload block. No page reloads, no console, reloading takes like a tenth of a second, and any tests I set up in ScratchX stay there.

Cool, but how does it work if it is not on *.github.io

Mrcomputer1 wrote:

What about right clicking the load extension button to load from file?

Ok

Jonathan50 wrote:

Znapi wrote:

I coded up a local server in Java to serve the extension fresh from my file system with every request(with no-cache headers to be safe), and a block that I can click to reload the extension in ScratchX.

Then, all I do to load the extension with a ScratchX link pointing to localhost, which gets auto completed by my browser. Then I just edit and save the extension, then click the reload block. No page reloads, no console, reloading takes like a tenth of a second, and any tests I set up in ScratchX stay there.

Cool, but how does it work if it is not on *.github.io

I don't think that rule is actually enforced. I'm not sure why they are telling us it is the only way to host an extension.

Znapi wrote:

Jonathan50 wrote:

Znapi wrote:

I coded up a local server in Java to serve the extension fresh from my file system with every request(with no-cache headers to be safe), and a block that I can click to reload the extension in ScratchX.

Then, all I do to load the extension with a ScratchX link pointing to localhost, which gets auto completed by my browser. Then I just edit and save the extension, then click the reload block. No page reloads, no console, reloading takes like a tenth of a second, and any tests I set up in ScratchX stay there.

Cool, but how does it work if it is not on *.github.io

I don't think that rule is actually enforced. I'm not sure why they are telling us it is the only way to host an extension.

Ok… I thought the extensions actually didn't work if they weren't. Hmm…..

Mrcomputer1 wrote:

What about right clicking the load extension button to load from file?

To add: along with this you can debug using your browser's Javascript console and that's how I read the error messages