You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to let you know that we just released a new version of LoadJS (v.3.6.0) that includes a couple of useful features:
First, v3.6.0 adds support for Promises via a returnPromise option:
varprom=loadjs(['/path/to/foo.js','/path/to/bar.js'],{returnPromise: true});prom.then(function(){/* foo.js & bar.js loaded */}).catch(function(pathsNotLoaded){/* at least one file didn't load */});
Second, v3.6.0 includes an important bugfix to detect cross-domain CSS load failures in Edge. Previously, load failures were triggering success callbacks but now they are being handled correctly. The source of the issue was lack of onerror support for cross-domain CSS files loaded via <link rel="stylesheet"> tags. To get around this issue, we are now using rel="preload" to load CSS files in Edge browsers.
Please try out the new features and let me know what you think!
Andres
The text was updated successfully, but these errors were encountered:
It's a little fiddly that the output of the loadJs function is now either a promise or not, it would be really handy to have a function akin to:
loadjs.await(...)
...which takes the same arguments as loadJs() and returns a promise, to enable wrapping of both functions independently without needing to coerce in an extra option.
Hi Everyone,
I just wanted to let you know that we just released a new version of LoadJS (v.3.6.0) that includes a couple of useful features:
First, v3.6.0 adds support for Promises via a
returnPromise
option:Second, v3.6.0 includes an important bugfix to detect cross-domain CSS load failures in Edge. Previously, load failures were triggering
success
callbacks but now they are being handled correctly. The source of the issue was lack ofonerror
support for cross-domain CSS files loaded via<link rel="stylesheet">
tags. To get around this issue, we are now usingrel="preload"
to load CSS files in Edge browsers.Please try out the new features and let me know what you think!
Andres
The text was updated successfully, but these errors were encountered: