gif-frames - npm Package Versions

[1.0.1] 2018-12-03

Changed

• Updated some dependencies to resolve security vulnerabilities reported by npm audit.

[1.0.0] - 2018-10-15

Added

• New API for getting frameInfo from gif (#9). Thanks @Snelius30!

Changed

• Using get-pixels fork which fetches frameInfo from omggif.

[0.4.1] - 2018-08-17

Changed

• Updated some dependencies to resolve security vulnerabilities reported by npm audit.

[0.4.0] - 2017-12-05

Added

• cumulative option for computing frames by layering on top of prior frames

Removed

• path import that was no longer being used

[0.3.0] - 2017-07-13

Added

• Unminified and minified browser bundles which will expose the library as a global called gifFrames - for those not using npm.

Changed

• Now relying on (hopefully short-term) forks of get-pixels and save-pixels, published to npm. These allow us to run UglifyJS for our minified build, and maintain compatibility with older browsers (the previous jpeg-js dependency relied on ES2015+ features).

[0.2.4] - 2017-06-26

Added

• This changelog
• Detailing of getImage and frameIndex in frame result object

Changed

• GIF type specification for get-pixels in the browser (see this issue)
• Improved/actually correct browser usage example
• getImageStream in frame result object now called getImage (since it can return a canvas element or a stream)

[0.2.3] - 2017-06-26

Added

• npm registry badge in readme

Changed

• Promise gets returned even if we bail during options validation

[0.2.2] - 2017-06-26

Added

• More terse intro code example included in readme

Changed

• Passing 'all' as frames option really works now (actually)

[0.2.1] - 2017-06-26

Changed

• Passing 'all' as frames option actually works now (almost! just kidding)

[0.2.0] - 2017-06-26

Added

• frames option for specifying which frames we want
• getFrames returns a Promise if available in environment
• Callback and promise pass a data stream for each requested frame
• Dependency on multi-integer-range

Changed

• Better browser usage example (but it doesn't work!)

Removed

• File writing - users can do that themselves (helps with interoperability between Node / browser)