Tom Pereira

Similarly, shouldn't the local click handler prevent navigation, if it doesn't return true? http://jsfiddle.net/Lc1am4ah/2/ Seems like the click handler fires after navigation..

Unfortunately, any script tags lower down the page that rely on something in an `async:false` script added using loadjs still appear to have a race condition - i.e. the loadjs-added...

This lack of idempotency is a shame, I was really under the impression `loadJs` was functionally equivalent to $script. The `require()` example is nice, but doesn't support the same script...

Yep - I guess this is a similar request to https://github.com/muicss/loadjs/issues/84 - if there's an easy way to set those flags innately in the library, would prevent a lot of...

I hadn't considered that hook, thanks! Would still be nice to have this embedded into the loader, however. I'm trying to keep the amount of code written to the page...

Yep, makes sense. I guess I'm just thinking if you have a lot of scripts to load, and each needs to add the `before:` code, it might be nice to...

great news on the promises support! 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...

+1 for this feature I have a situation where I need to modify something in a `:before` and `:after` pseudo-element from JS; inaccessible normally, but can be modified if a...

Hmm... I appear to have an invalid npm package - the `CHANGELOG.md` I have is for `v2.0.0` yet the package.json talks of `2.1.0` Apologies if this is the ultimate cause...

I think what's been published to npmjs.com is incorrect - see: https://www.npmjs.com/package/postcss-reference?activeTab=code ...this doesn't match the head of the repo. I fear the `package.json` is still at `2.0.0` and `2.1.0`...