exiftool-vendored - npm Package Versions

v29.1.0

• 🌱 Upgraded ExifTool to version 13.17. Note that this release includes seventeen ExifTool version bumps (from November 2024 through January 2025--Phil Harvey has been busy!). Although I haven't seen any breaking changes in the Tags generation or test suite with the new versions, please do your own validation.

• ✨ Thanks to Mert for adding forceWrite to binary tag extraction.

• ✨ ExifTool's Geolocation feature seems to work around some obscure GPS encoding issues where the decimal sign gets ignored. This project now leverages that "corrected" GPS location by adopting the hemisphere signs, which seems to fix this issue.

• 🐞 Removed OffsetTime from the list of Timezone offset tags we infer tz from. Thanks for the heads-up, Carsten Otto!

• 📦 Updated to the latest eslint, which required rewriting the config, and delinting the new nits

• 📦 Deleted most of the prettier config to accept their defaults. This created a huge no-op commit but now it's over.

v29.0.0

• 💔/🐞/📦 ExifTool sometimes returns boolean values for some tags, like SemanticStylePreset, but uses "Yes" or "No" values for other tags, like GPSValid (TIL!). If the tag name ends in Valid and is truthy (1, true, "Yes") or falsy (0, false, "No"), we'll convert it to a boolean for you. Note that this is arguably a breaking API change, but it should be what you were already expecting (so is it a bug fix?). See the diff to the Tags interface in this version to verify what types have changed.

• 📦 Reduced streamFlushMillis to 10. This reduced elapsed time for the full test suite by 2.5x on macOS and 3x on Windows, and drops the upper latency bound substantially. Note that this is at the risk of buffered stream collisions between tasks. The (extensive) test suite on Github Actions (whose virtual machines are notoriously slower than molasses) still runs solidly, but if you see internal errors, please open a Github issue and increase your streamFlushMillis.

• 💔 TypeScript now emits ES2022, which requires Node.js 18.

GPS improvements

• 🐞/📦 GPS Latitude and GPS Longitude values are now parsed from DMS notation, which seems to avoid some incorrectly signed values in some file formats (especially for some problematic XMP exports, like from Apple Photos). Numeric GPSLatitude and GPSLongitude are still accepted: to avoid the new coordinates parsing code, restore GPSLatitude and GPSLongitude to the ExifToolOptions.numericTags array.

• 🐞/📦 If ExifToolOptions.geolocation is enabled, and GeolocationPosition exists, and we got numeric GPS coordinates, we will assume the hemisphere from GeolocationPosition, as that tag seems to correct for more conditions than GPS*Ref values.

• 🐞/📦 If the encoded GPS location is invalid, all GPS* and Geolocation* metadata will be omitted from ExifTool.readTags(). Prior versions let some values (like GPSCoordinates) from invalid values slip by. A location is invalid if latitude and longitude are 0, out of bounds, either are unspecified.

• 🐞/📦 Reading and writing GPS latitude and GPS longitude values is surprisingly tricky, and could fail for some file formats due to inconsistent handling of negative values. Now, within ExifTool.writeTags(), we will automatically set GPSLatitudeRef and GPSLongitudeRef if lat/lon are provided but references are unspecified. More tests were added to verify this workaround. On reads, GPSLatitudeRef and GPSLongitudeRef will be backfilled to be correct. Note that they only return "N" | "S" | "E" | "W" now, rather than possibly being the full cardinal direction name.

• 🐞 If ignoreZeroZeroLatLon and geolocation were true, (0,0) location timezones could still be inferred in prior versions.

• 📦 GPS coordinates are now round to 6 decimal places (≈11cm precision). This exceeds consumer GPS accuracy while simplifying test assertions and reducing noise in comparisons. Previously storing full float precision added complexity without practical benefit.

v28.8.0

Important: ExifTool versions use the format NN.NN and do not follow semantic versioning. The version from ExifTool will not parse correctly with the semver library (for the next 10 versions) since they are zero- padded.

• 🌱 Upgraded ExifTool to version 13.00

  Note: ExifTool version numbers increment by 0.01 and do not follow semantic versioning conventions. The changes between version 12.99 and 13.00 are minor updates without any known breaking changes.

• 📦 Added Node.js v23 to the build matrix.

v28.7.0

• 🌱 ExifTool upgraded to version 12.99

v28.6.0

• 🌱 ExifTool upgraded to version 12.97

• 📦 Fields in Tags sub-interfaces are correctly sorted

v28.5.0

• 🐞/📦 Add new ExifToolOptions.preferTimezoneInferenceFromGps to prefer GPS timezones. See the jsdoc for details.

• 🐞 Support triple-deep IANA timezones, like America/Indiana/Indianapolis.

v28.4.1

• 📦 The warning "Invalid GPSLatitude or GPSLongitude. Deleting geolocation tags" will only be added if GPSLatitude or GPSLongitude is non-null.

v28.4.0

• ✨ Add workaround for abberant Nikon TimeZone encoding. Addresses #215. Set ExifToolOptions.adjustTimeZoneIfDaylightSavings to () => undefined to retain prior behavior.

v28.3.1

• 🐞 Re-add +13:00 as a valid timezone offset. Addresses #214.

v28.3.0

• 🌱 ExifTool upgraded to v12.96

• ✨ Add support for timezone offset extraction from TimeStamp. Note that this is disabled by default to retain prior behavior (and due to me being chicken that this might break other random cameras). Addresses #209

• ✨ @bugfest improved write typings around Structs. Thanks! See #212

• 🐞 @noahmorrison found and fixed an issue with inferLikelyOffsetMinutes. Thanks for the assist! See #208 for details.

• 📦/💔 Possible breaking change: several archane timezone offsets were removed from the ValidTimezoneOffsets array, to better address #208.