- svg.js: The esm bundle
- svg.min.js: The bundle for all browsers for maximum support
- svg.node.js: The bundle for node
- polyfill.js: Using svg.min.js requires this polyfill in case the Browser does not understand all of ./config/polyfillList.js
- polyfillIE.js: This is required when you use IE11 (polyfill.js still required)

Please note, that not all test pass for IE11 due to its rounding issues and wrong calculation of bbox.
Also note, that `defaultPrevented` is not working for CustomEvents in IE11.

- words() and element() added to Dom
- svg() now returns the _parent_ of the imported element, when outerHTML is true (which means an element gets replaces)

- refactor code into functions
- handle timeSource correctly
- allow for immediate updates
- Runners dont know about their delay anymore. Thats far more simple.
- Timeline is paused on creation

This is great - we should party hard. I mean - it took like 4 month to get this done. That's way to much! I don't want anymore. Pease send help :D

This commit refactors the getOrigin helper, in order to send the origin to the correct
space. The origin should be expressed in the space of the last animation.

Changes
=======
- Refactored the getOrigin helper
- Added a simple example to the dirty file to test multiple transformations

This commit uncovered an issue with the relative non-affine transformations. It is
now correctly fixed and working. Next we should fix the affine transforms as well.

Changes
=======
- Fixed the relative non-affine transformation animations

This commit finds an error in the scheduling duration that we need to fix.

This commit adds an example that demonstrates how I'd imagine declarative animations
should work and how they should mirror what imperative animations would do

Changes
=======
- Added a simple declarative example

This commit fixes the transformations and allows single animated
transformations to properly work.

This commit attempts to modify the origin on each frame, but it seems
that we have some kind of bug that we need to fix first

This commit allows us to apply more than one transform to an element, and
have them correctly applied to the element.

This commit slightly modifies the behaviour of absolute transforms,
we will get them working soon :D

This commit start to remove the expensive bbox calculation by assuming
that the origin stays at a fixed point during an animation. This is a
good assumption as transforms don't change the bbox of the element.

Changes
=======
- Refactor the Element.transform function
- Make a getOrigin function to call the bbox only one time

This commit finally gets transformations workin in both absolute and
relative mode. This is the last **major** hurdle for the new
animation module, so we just need to clean it up and fix some bugs 🐞