Fast, cross-platform Node.js access to ExifTool
Full Changelog: https://github.com/photostructure/exiftool-vendored.js/compare/v25.1.0...v25.2.0
✨ Added retain
field to ExifTool.deleteAllTags
to address #178
📦 Added jsdocs for many Tag
interface types
📦 Expose GeolocationTags
and isGeolocationTag()
📦 Add FileTags.FileCreateDate
(only a thing on Windows)
🌱/✨ ExifTool upgraded to v12.80, which adds support for reverse-geo lookups and [several other geolocation features](https://exiftool.org/geolocation.html
✨ If no vendored version of exiftool
is available, we'll try to make do with whatever is available in the PATH
.
✨ ExifToolOptions.exiftoolPath
can now be an async
function
✨ Added Geolocation Tags. These will only be available if {geolocation: true}
is passed to the ExifTool constructor.
📦 Added support for electron-forge
: see the docs for details.
🌱 ExifTool upgraded to v12.78
📦 Added ExifTool.off
🌱 ExifTool upgraded to v12.76. Note that an ARW file corrupting issue was found that's existed since v12.45.
📦 Updated dependencies, including new batch-cluster v13 🍀
Full Changelog: https://github.com/photostructure/exiftool-vendored.js/compare/v24.4.0...v24.5.0
🌱 ExifTool upgraded to v12.73.
📦 If the underlying Perl installation is invalid, throw an error. See #168 for details.
🌱 ExifTool upgraded to v12.72.
📦 Relax GPS latitude/longitude parser to handle invalid Ref values (a warning will be appended to the Tags.warnings field). See #165.
ncu -u
(e2b899e)perl
isn't installed in /usr/bin
, feed the full path to perl
(if we can find it) to spawn
(rather than relying on the shell to use $PATH
). This should address issues like #163
perl
doesn't live in /usr/bin. Fixes #163. (b42526c)isWarning()
detection to be simply /warning:/i
. v24.0.0 would throw errors when extracting binary thumbnails due to issues like "Warning: Ignored non-standard EXIF at TIFF-IFD0-JPEG-APP1-IFD0", which is decidedly a warning. ExifTool.write
now leans (hard) on returning .warnings
rather than throwing errors: It is up to you to inspect .warnings
and decide for your own usecase if the issue is exceptional. See issue #162 for details.