David DeSandro

Thanks for reporting this issue. I'll have to take a look.

I am unable to reproduce this bug. Here's a reduced test case to get started: http://codepen.io/desandro/pen/zvdzLj

Thanks for this feature request. **Add a 👍 reaction** to this issue if you would like to see see flickity-fade get a TypeScript definition file.

Thanks for reporting this issue. I'll take a look.

Thank you for this proposal. **Add a 👍 reaction to this issue** if you'd like see Metafizzy build an SVG animation library.

Thank you for this feature request. Flickity does not support `` at this time. **Add a 👍 reaction** to this issue if you would like to see this feature added....

Thanks for reporting this issue. This issue is dependent on metafizzy/flickity#113

Thanks for this contribution. This may resolve the bug in some instances. In my experience I've found it causes issues with poor rendering due to sub-pixel alignment. I'll keep this...

bower's `main` has been poorly defined in the past. While previous versions of Outlayer did include `item.js` in `main`, Outlayer v1.3 has adopted a new specification for `main`. See bower/bower.json-spec#43....

Tried working on this today. I've found part of the problem is in [`Item.getPosition`](https://github.com/metafizzy/outlayer/blob/v2.0.1/item.js#L130-L134), calculating the current position from `getComputedStyle`. With testing Outlayer, it returns the previous value. For example,...