Closed RomkeVdMeulen closed 6 years ago
Seems like browsers started to respect the whatwg recommendations.. that might lead to reorganizing router redirects as well.. )-: sad day (-:
Just ran into this again. Has anyone had a chance to look at this?
@EisenbergEffect Can you or somebody on your team please take a look at this?
I can get this merged and released if @RomkeVdMeulen can remove the changes to the dist folder. Those will get generated when I run the build. Ping me after that's done and I'll merge it and put out a release.
Apologies for the delay. This just went under the radar somehow.
Done.
Thanks!
Need a bit more time to get the actual release out. It will probably be Monday-ish.
When used in combination with async / await, the value that the promise is rejected with may be thrown, and throwing a string literal rather than an Error may cause warnings in some browsers.
In my case (using headless Chrome), I got "Error: the string "Element not found" was thrown, throw an Error :)". This obscured the trace of the actual rejected promise.