Triggering error paths in require.js about fwrequirejs HOT 1 CLOSED

Hmm, I guess I forgot to save my comment before committing the fix...

Thanks for the detailed reply!

The fireworks env looks like it is sync script loading/evaluation, which simplifies some things.

Yes, calling fw.runScript(url) tells the app to synchronously load and evaluate a script. There’s no way to do async loading.

If you wanted to tie into the errbacks use in requirejs 2.0, that would take a bit more work, playing with some of the internals.

I was mostly wondering whether there was a defined way for adapters to handle errbacks and path fallbacks, just so I could do the right thing. But I’m not sure it's actually needed this in this environment, as there’s no way to load anything over the wire. If a required script doesn’t exist at the specified path, it's a bug, and it should be caught before a developer releases the script.

You could format the error so that it has an error.requireModules = [moduleName] instead of error.module = moduleName;, and use an error.requireType = 'scripterror', if you want it to look more like an error that is generated from the regular requirejs code.

That’s a good idea. I’ll add that.

from fwrequirejs.