All Versions
196
Latest Version
Avg Release Cycle
7 days
Latest Release
91 days ago

Changelog History
Page 13

  • v6.0.1 Changes

    • ๐Ÿ“ฆ Typedoc fails to render Partial<> composites, so mktags now renders each Tag as optional. The Tag interface should be exactly the same as from v6.0.0.
  • v6.0.0 Changes

    • ๐Ÿ’” ExifTool's many constructor parameters turned out to be quite unweildy. Version 6's constructor now takes an options hash. If you used the defaults, those haven't changed, and your code won't need to change.
    • ๐Ÿ’” ExifTool.enqueueTask takes a Task thunk now, to enable cleaner task retry code. I don't expect many consumers will have used this API directly.
    • ๐Ÿž In prior versions, when maxTasksPerProcess was reached, on some OSes, the host process would exit.
    • โœจ Rebuilt Tags based on new phone and camera models
    • ๐Ÿ‘€ ๐Ÿ“ฆ Files are not stated before passing them on to ExifTool, as it seems to be faster on all platforms without this check. If you were error-matching on ENOENT, you'll need to switch to looking for "File not found".
    • โšก๏ธ ๐Ÿ’” BatchCluster was updated, which has a robust PID-exists implementation, but those signatures now return Promises rather than being synchronous, so the exported running function has changed to return a Promise<number[]>.
    • โฌ†๏ธ ๐ŸŒฑ ExifTool upgraded to v11.09.
  • v5.5.0 Changes

    • โฌ†๏ธ ๐ŸŒฑ ExifTool upgraded to v11.08.
  • v5.4.0 Changes

    • โœจ Some photo sharing sites will set the CreateDate or SubSecCreateDate to invalid values like 0001:01:01 00:00:00.00. These values are now returned as strings so consumers can more consistently discriminate invalid metadata.
  • v5.3.0 Changes

    • โœจ Prior versions of ExifTool.read() always added the -fast option. This read mode omits metadata found after the image payload. This makes reads much faster, but means that a few tags, like OriginalImageHeight, may not be extracted. See https://sno.phy.queensu.ca/~phil/exiftool/#performance for more details.

    Cuneytt reported this and I realized I should make -fast a user preference. To maintain existing behavior, I've made the optional second argument of ExifTool.read default to ["-fast"]. If you want to use "slow mode", just give an empty array to the second argument. If you want -fast2 mode, provide ["-fast2"] as the second argument.

  • v5.2.0 Changes

  • v5.1.0 Changes

    • โœจ new exiftool.rewriteAllTags(), which may repair problematic image metadata.
    • โฌ†๏ธ ๐ŸŒฑ ExifTool upgraded to v11.02.
    • 0๏ธโƒฃ ๐Ÿ“ฆ taskRetries default is now 1, which should allow recovery of the rare RPC/fork error, but actual corrupt files and realy errors can be rejected sooner.
    • โœ… ๐Ÿ“ฆ Pull in latest dependencies, include new batch-cluster.
  • v5.0.0 Changes

    • ๐Ÿ’”/โœจ Task rejections are always Errors now, and ExifTool.on observers will be provided Errors on failure cases. Previously, rejections and events had been a mixture of strings and Errors. I'm bumping the major version just to make sure people adjust their code accordingly, but I'm hoping this is a no-op for most people. Thanks for the suggestion, Nils Knappmeier!
  • v4.26.0 Changes

    • โฌ†๏ธ ๐ŸŒฑ ExifTool upgraded to v11.01. Note that ExifTool doesn't really follow semver, so this shouldn't be a breaking change, so we'll stay on v4.
    • โœ… ๐Ÿ“ฆ Pull in latest dependencies, including batch-cluster and TypeScript.
    • ๐Ÿ“ฆ Fix version spec because exiftool now has a left-zero-padded version that semver is not happy about.
  • v4.25.0 Changes

    • โฌ†๏ธ ๐ŸŒฑ ExifTool upgraded to v10.98