+ Better handling of simultaneously loaded components ([#12](#12) - thanks **[@vgavro](https://github.com/vgavro)**)
+ Emit vue events for `loaded` and `error` ([#31](#31) - thanks **[@vgavro](https://github.com/vgavro)**)
+ Updated all dev dependencies and switched from uglify to terser

#29)

* setting loading promise on request (not on load) to avoid duplicate loadings before load were finished

* fixes for setting loading promise instead of 1

* fixed verbose prop async=false (will act as async=true previously); added load and error events

…itis

* Decode html entities

* Update index.js

* Update index.js

* Update index.js

- IE Support (via **[@akhoury](https://github.com/akhoury)**)
- Use `render` function instead of `template` (via **[@bichikim](https://github.com/bichikim)**)
- Updated dependencies
- Removed broken `grunt-rollup` and updated `Gruntfile.js` accordingly

Now injects the script properly with Vue's `render` function thanks to @bichikim

IE Support

see #17

fix #9 null/undefined crossorigin params handling

…i 9 will cause error

Fixes #5 crossorigin in HTML is crossOrigin in DOM

This should fix the issue where the crossorigin property was not
being written out to the script tag in the DOM. The HTML
property is all lower case, but the DOM spec requires it to
be camel cased.

See:

w3c/webappsec-subresource-integrity#24
https://html.spec.whatwg.org/multipage/embedded-content.html#dom-img-crossorigin

This commit doesn't change any behavior due to a lucky bug.
I had some code to "support" IE, but it was wrong. Thankfully, its
wrongness was ameliorated by a bug (`this` being bound to something
else due to arrow-function usage). I've now simply removed the IE-specific
support as the latest versions of IE should support .onerror and .onload