All Versions
Latest Version
Avg Release Cycle
46 days
Latest Release
1871 days ago

Changelog History

  • v3.0.3 Changes

    October 19, 2018

    ๐Ÿ›  Fix to work with styled-components v4

    ๐Ÿš€ Patch release to add support for styled-components v4.

    ๐Ÿš€ Big thanks to @morleyzhi for their work in this release!

  • v3.0.2 Changes

    September 03, 2018

    โž• Add verticalAlignment to API docs

    ๐Ÿ“š A prop was missing from the documentation! Thanks to @everdimension for catching and fixing :)

  • v3.0.1 Changes

    January 30, 2018

    ๐Ÿ›  Fix Typescript bindings

    ๐Ÿš€ Quick patch release to fix a bug with Typescript bindings.

    Thanks to @vsaarinen for the PR, and @thupi for letting me know / troubleshooting the issue!

  • v3.0.0 Changes

    January 14, 2018

    ๐Ÿ”– Version 3.0

    ๐Ÿšš Switch to Rollup bundler, remove polyfills and deprecations.

    ๐Ÿš€ The major feature of this release is size reduction. Gzip size of the module has gone from over 6kb to 4905 bytes (4.79kb). Woohoo!

    ๐Ÿ—„ The major factor in this reduction was moving from Webpack to Rollup. We were also able to kill some deprecations, which lightened the bundle.

    ๐Ÿ’ฅ Breaking changes

    1. Switch from polyfills to helper functions

    Before, we were polyfilling certain array methods: find, every, and isArray. This wasn't ideal, since it meant we could be patching the host application's array methods.

    ๐Ÿ’ป We still include helper methods to perform these operations, so browser support has not changed. But, if your host application (the code you write) uses the aforementioned array methods, they may suddenly not work in legacy browsers like Internet Explorer, since our polyfills have been removed.

    ๐Ÿšš 1. Removed typo animation presets

    If you ask me, "accordion" should really be spelled "accordian". That's how you pronounce it!

    ๐Ÿ‘ That said, the correct spelling is "accordion". For the presets accordionHorizontal and accordionVertical, we were supporting both variants, but now only the correct spelling will be accepted.

    ๐Ÿšš 1. Removed deprecated prop "disableAnimations"

    We renamed the prop disableAnimations to disableAllAnimations. The former will no longer work.

    ๐Ÿš€ Thanks a ton to @Andarist for their work contributing all the major parts of this release. Also thanks to @tobilen and @Hypnosphi for reviewing the PRs associated with this release.

  • v2.10.2 Changes

    January 10, 2018

    โž• Add warning when children are disabled

    ๐Ÿšš In Internet Explorer 11 (and below), the transitonend event will not (consistently) fire for elements that have the disabled attribute. This means the callback for node removal is never fired and the supposedly removed nodes stay in the html.

    ๐Ÿ Also includes some cleanup, and a move to use cross-env for Windows support.

    ๐Ÿš€ Thanks a ton to @tobilen for contributing this release!!

  • v2.10.1 Changes

    January 05, 2018

    ๐Ÿ“š Performance Improvements, typescript type fixes, documentation update

    ๐Ÿš€ The largest change in this release is an optimization to batch calls that cause layout recalculation. For large lists, this can improve the performance of the calculations required to begin the animation by a tremendous amount (4x in one recorded instance!).

    ๐Ÿ“š This release also features some fixes to the Typescript types, as well as a tweak to the documentation to make it more accurate.

    ๐Ÿš€ Huge thanks to @egorshulga, who contributed all of the aforementioned work in this release!

  • v2.10.0 Changes

    November 26, 2017

    Wrapperless Mode

    ๐Ÿšš Prior to React 16, a React component had to return a single top-level element. This meant that React Flip Move had to wrap its children in a <div> or other HTML node; it couldn't just return the array of children provided to it.

    ๐Ÿšš Happily, React's new reconciliation engine in v16 changes this, and React Flip Move can now be run in "wrapperless" mode, which means that it won't create an additional node.

    To use this new mode, simply set typeName to null.

    ๐Ÿšš There may be some quirks. For example, React Flip Move still needs to position its children to handle leave animations, and so if <FlipMove>'s parent container is set to position: static (the default), you may notice some quirky behaviour. To fix this, just set position: relative (or absolute/fixed) on the parent.

    Huge thanks to @tobilen for their work on this feature, and to @Hypnosphi for reviewing.

  • v2.9.17 Changes

    October 15, 2017

    โž• Adds support for React 16, and brings the Flip Move dev environment into 2017 ๐ŸŽ‰ ๐ŸŽ‰ ๐ŸŽ‰

    โšก๏ธ While this sounds like a small change, it's a complete overhaul of the dev dependencies. Our tests and stories have been updated.

    Huge huge thanks to @tobilen for their work on this, and @Hypnosphi for the in-depth reviews. Makes me so happy that there's a community of developers contributing to this project :D

  • v2.9.16 Changes

    October 15, 2017

    ๐Ÿ›  Fix bugs with IE 10 and node type check

    ๐Ÿ›  This release includes two bugfixes:

    • ๐Ÿ‘ Allow FlipMove to work within iFrames (via React 16 portals) - #193
    • ๐Ÿ›  Fix issue with IE10 not able to access this.props = #194

    ๐Ÿš€ Big thanks to @AlexDunmow and @nicolasraynaud-millevolts for their work on this release! ๐ŸŽ‰

  • v2.9.15 Changes

    August 28, 2017

    ๐Ÿ›  Fix zombie nodes (#120) and increase test stability

    ๐Ÿš€ This release fixes the often-reported issue with zombie nodes staying after fast toggling. Huge thanks to @tobilen for tackling this problem!!

    ๐Ÿš€ This release also includes some improvements to our tests, by polyfilling requestAnimationFrame. Huge thanks to @Hypnosphi for their work on this, and for everything they've done and continue to do for this project :D