willscott
commented
10 years ago Yeah. the browsers don't give you a useful stack trace when there's a parse error when loading a script into a web worker with importScripts.
The easiest way to debug is to configure freedom to use port:"frame" temporarily to load the freedom containers into iframes rather than webworkers.
Will use this bug for tracking documentation and clearer error message for how to procede in this case, because it has come up several times.
Test case: insert a syntax error into an identity provider that is provided asynchronously. There's no parse error in the console log; the only indication that something failed is the later stack trace when trying to instantiate the provider.