77 KiB
Changelog/Versioning
Versioning
Providing the flexibility to reversion the API or UPDATE version slots as features or bugfixes arise and using ExifTool's version number is at odds with each other, so this library follows Semver, and the vendored versions of ExifTool match the version that they vendor.
The MAJOR or API version is incremented for
- 💔 Non-backward-compatible API changes
- 🏚️ End of life versions of Node.js are dropped from the build matrix
The MINOR or UPDATE version is incremented for
- 🌱 New releases of ExifTool
- 🔥 Security updates
- ✨ Backwards-compatible features
The PATCH version is incremented for
- 🐞 Backwards-compatible bug fixes
- 📦 Minor packaging changes
Version history
v30.0.0
-
💔 Dropped support for Node v18, whose End-of-Life was 2025-04-30.
-
🌱 Upgraded ExifTool to version 13.29.
-
✨ Added new
TagNamesstring enumeration with the most popular 2,500(ish) tag field names that is automatically updated bymktags. As a reminder: theTagsinterface is not comprehensive. If we're missing any of your favorite fields, open an issue with an attached example media file and I look into promoting it to a "guaranteed" status (like we've done with several hundred fields already). -
📦 Renamed the
.tzfield inTagsto.zone. Note that for the next few releases,.tzwill be kept, but marked as deprecated. After doing a bit of research, it turns out the correct term for identifiers likeAmerica/Los_Angeleswithin the IANA Time Zone Database is "zone." The "tz" term commonly refers to the entire Time Zone Database, or "tz database" (also called tzdata or zoneinfo). -
✨ Updating to new versions of ExifTool is now fully automated via GitHub Actions.
v29.3.0
-
🌱 Upgraded ExifTool to version 13.26.
-
✨ Added support for keepUTCTime to ExifToolOptions. This is a new ExifTool feature specifically for unixtime-encoded datetimes, but seems to be rarely applicable as unixtime is not a valid encoding format for most datetime tags.
v29.2.0
-
🌱 Upgraded ExifTool to version 13.25.
-
✨ ExifTool.write now supports
booleanfield values. Thanks for the suggestion, Kira-Kitsune. -
📦 Updated the default for maxProcs to use availableParallelism where available.
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
OffsetTimefrom 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
prettierconfig to accept their defaults. This created a huge no-op commit but now it's over.
v29.0.0
-
💔/🐞/📦 ExifTool sometimes returns
booleanvalues for some tags, likeSemanticStylePreset, but uses "Yes" or "No" values for other tags, likeGPSValid(TIL!). If the tag name ends inValidand 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
streamFlushMillisto10. 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 yourstreamFlushMillis. -
💔 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
GPSLatitudeandGPSLongitudeto theExifToolOptions.numericTagsarray. -
🐞/📦 If
ExifToolOptions.geolocationis enabled, andGeolocationPositionexists, 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*andGeolocation*metadata will be omitted fromExifTool.readTags(). Prior versions let some values (likeGPSCoordinates) 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 setGPSLatitudeRefandGPSLongitudeRefif lat/lon are provided but references are unspecified. More tests were added to verify this workaround. On reads,GPSLatitudeRefandGPSLongitudeRefwill 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
ignoreZeroZeroLatLonandgeolocationweretrue, (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
Tagssub-interfaces are correctly sorted
v28.5.0
-
🐞/📦 Add new
ExifToolOptions.preferTimezoneInferenceFromGpsto 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
GPSLatitudeorGPSLongitudeis non-null.
v28.4.0
- ✨ Add workaround for abberant Nikon
TimeZoneencoding. Addresses #215. SetExifToolOptions.adjustTimeZoneIfDaylightSavingsto() => undefinedto 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
ValidTimezoneOffsetsarray, to better address #208.
v28.2.1
- 📦 Add
snyk-linuxto npmignore to fix #200
v28.2.0
- 🌱/✨/🐞 ExifTool upgraded to v12.91. Notably, the shebang line has changed from
/usr/bin/perlto/usr/bin/env perl. The exiftool-vendored.pl package works around a new error from this shebang line.
v28.1.0
-
📦 Add tests for #187
-
📦 Export
ImageDataHashTaginterface
v28.0.0
-
🌱/✨/🐞 ExifTool upgraded to v12.89. Notably, ExifTool on Windows is now using the "official" packaging. This should be equivalent to prior builds, as exiftool-vendored.exe was already using Oliver Betz's perl launcher.
-
💔 Prior versions included
APP1Tags,APP4Tags,APP5Tags,APP6Tags,APP12Tags, andAPP14Tags. Unfortunately, due to field name duplications, fields could hop between these interfaces between versions. These have all been collapsed into a single newAPPTags. -
✨ Added support for old Sony A7 UTC inference. Thanks for the help, Friso Smit!
-
✨ Added support for Android Motion Photos. Thanks for the help, Lukas!
-
📦 Updated
ReadTaskandWriteTaskconstructors to be public as well as the.parse()methods as a workaround for #190 -
📦 Fought AND WON a very obscure issue with Node v22.5.0
v27.0.0
-
💔
ExifToolOptions.structis now"undef" | 0 | 1 | 2. See #184 -
✨
ExifToolOptionsnow includesreadArgsandwriteArgs, which can be specified both atExifToolconstruction, as well as calls toExifTool.readandExifTool.write. The prior method signatures are deprecated.
v26.2.0
-
✨ Support for all ExifTool
structmodes (fixes #184). See ExifToolOptions.struct for details. -
📦 Fix documentation to reference ExifTool.read() (fixes #183)
v26.1.0
-
🌱/✨/🐞 ExifTool upgraded to v12.85. Notably, this addresses reversed HEIC orientation.
-
🐞 Perhaps address Perl not installed error.
v26.0.0
-
🌱/✨ ExifTool upgraded to v12.84
-
📦 Support disabling
-ignoreMinorErrorsto work around shenanigans like #181. This is an optional field that defaults to prior behavior (enabled, which ignores minor errors, which is normally desired, but has some side effects like fully reading tags that may be extremely long). See ExifToolOptions.ignoreMinorErrors for details. -
📦 ExifTool on Windows was upgraded to Strawberry Perl 5.32.1
v25.2.0
-
🌱/✨ ExifTool upgraded to v12.82
-
📦 Add support for
NODE_DEBUG=exiftool-vendored -
📦 Export
exiftoolPath()so custom implementations can use it as a fallback (or default, and provide their own fallback)
v25.1.0
-
✨ Added
retainfield toExifTool.deleteAllTagsto address #178 -
📦 Added jsdocs for many
Taginterface types -
📦 Expose
GeolocationTagsandisGeolocationTag() -
📦 Add
FileTags.FileCreateDate(only a thing on Windows)
v25.0.0
-
🌱/✨ ExifTool upgraded to v12.80, which adds support for reverse-geo lookups and several other geolocation features
-
✨ If no vendored version of
exiftoolis available, we'll try to make do with whatever is available in thePATH. -
✨
ExifToolOptions.exiftoolPathcan now be anasyncfunction -
✨ 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.
v24.6.0
-
🌱 ExifTool upgraded to v12.78
-
📦 Added ExifTool.off
v24.5.0
-
🌱 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 🍀
v24.4.0
-
🌱 ExifTool upgraded to v12.73.
-
📦 If the underlying Perl installation is invalid, throw an error. See #168 for details.
v24.3.0
-
🌱 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.
v24.2.0
- 🐞 If
perlisn't installed in/usr/bin, feed the full path toperl(if we can find it) tospawn(rather than relying on the shell to use$PATH). This should address issues like #163
v24.1.0
- 📦 Relaxed
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.writenow leans (hard) on returningTags.warningsrather than throwing errors: It is up to you to inspect.warningsand decide for your own usecase if the issue is exceptional. See issue #162 for details.
v24.0.0
-
💔 In the interests of reducing complexity, the
ExifToolOptions.isIgnorableErrorpredicate field was removed -- if this was used by anyone, please open an issue and we can talk about it. -
💔
ExifTool.writenow returns metadata describing how many files were unchanged, updated, or created, and no longer throws errors if the operation is a no-op or inputs are invalid. See issue #162 for details. -
✨
.warningsare returned byExifTool.readandExifTool.writetasks if there are non-critical warnings emitted tostderrby ExifTool. -
📦 Some fields in
Tagswere moved to more correct groups -
📦 Refined
WriteTagssignature to omitExifToolTagsandFileTagsfields. -
📦 Added
node:prefix to Node.js module imports. This requires node v14.13, v16.0, or later.
v23.7.0
-
📦 Added MWG
.HierarchicalKeywordsand.CollectionstoTags -
🐞/📦
Rotationwas removed from the default set ofnumericTags, as it may be encoded as an EXIF orientation value, or a degree rotation, and it should be up to the application to figure it out.
v23.6.0
-
📦 Added new option,
ignoreZeroZeroLatLon, and defaulted this new option totrue. Several camera manufacturers and image applications will write0to theGPSLatitudeandGPSLongitudetags when they mean "unset"--but this can cause incorrect timezone inference. Set tofalseto retain prior code behavior. -
📦
Rotationwas added to the default set ofnumericTags, as it may be encoded as an EXIF orientation value. Prior builds could return Rotation values like"Rotate 270 CW". -
📦
XMPTags.Noteswas added toTags, used as an album description -
🐞 Some
ExifToolOptions were not passed from ExifTool into the ReadTask, which caused ReadTask to revert to defaults.
v23.5.0
-
🌱 ExifTool upgraded to v12.70. 🏆 Thanks for 20 years of updates, Phil Harvey! 🏆
-
📦
XMPTags.Albumwas added toTags
v23.4.0
-
🌱 ExifTool upgraded to v12.69
-
📦
ExifTool.read:ExifTimenow adopts the default zone extracted from the file. This may result in different values for timestamps. -
📦 Updated dependencies
v23.3.0
- 🐞 Restored datestamp parsing of
ResourceEvent.When
v23.2.0
-
✨ Timezone parsing improvements:
- Added
ExifToolOptions.inferTimezoneFromDatestampTags. - Timezone inference from datestamps now skips over UTC values, as Google Takeout (and several other applications) may spuriously set "+00:00" to datestamps.
- ReadTask.parse in prior versions had to scan all tags twice to set the timezone. Code was refactored to do this in a single pass.
- Timezone extraction and normalization was improved.
- Added
-
📦 Add
creationDateto CapturedAtTagNames. See PR#159.
v23.1.0
-
🌱 ExifTool upgraded to v12.67
-
✨
ExifTimenow parses and stores timezone offsets if available. This resolves issue #157. -
📦
ExifDateTime,ExifTime, andExifDateare now only allowed to try to parse keys that includesdateortime, which avoids incorrect parsing of tags likeMonthDayCreated(which looks like12:19) -
📦 Updated all dependencies, but only
devDependencieswere impacted.
v23.0.0
-
🏚️ Dropped support for Node.js v16, which is End-of-Life.
-
💔/🐞 If
defaultVideosToUTCis set totrue,read()will now allow non-UTC timezones extractable from other tags to be assigned to.tz. Prior versions would simply force.tzto "UTC" for all videos, which wasn't great. Note that "UTC" is still used as the default timezone for all datestamps without explicit timezones, just as prior versions did. See issue #156 for details. -
💔
backfillTimezonesnow defaults totrue. Although this is likely to be what people expect, but know that this makes the assumption that all encoded times without an explicit offset share the same tz, which may not be correct (say, if you edit the image in a different timezone from when it was captured). -
💔 If
backfillTimezonesis set tofalse,ExifDateTimewill no longer use the current file's.tzas a default. Prior versions would inherit the file's.tz, which might be incorrect. -
📦
ExifDateTimenow includes an.inferredZonefield, which may be useful in helping to determine how "trustworthy" the zone and actual datestamp value is.
v22.2.3
- 🐞 Apply the v22.2.3 bugfix even wider (just found a
SubSecTimevalue of "01" in the wild, and it was happily parsed into today's date, oops).
v22.2.2
- 🐞 Apply the v22.2.1 bugfix wider: we now reject parsing any date-ish or time-ish value that matches
/^0+$/.
v22.2.1
- 🐞
ExifTimenow properly rejects invalidSubSecTime,SubSecTimeOriginal, ... values of "0" or "00".
v22.2.0
-
✨ Add support for zone extraction from
ExifDateTime,ExifTime,number[], andnumberfields. -
📦 Improve type signature of
extractTzOffsetFromTags.
v22.1.0
-
🌱 ExifTool upgraded to v12.65
-
✨ Add support for new
ImageDataHashtag: See the docs for details. -
🐞
perlis checked for on non-windows machines at startup. This resolves #152. You can disable this with the newcheckPerloption.
v22.0.0
-
🏚️ Drop support for Node 14, which EOL'ed 2023-04-30
-
🌱 ExifTool upgraded to v12.62
-
🐞 Fix exports for DefaultExifToolOptions and several other non-type values. Thanks for the bug report, renambot!
v21.5.1
-
📦 Avoid double-rendering of ImageDataMD5 (Thanks, Phil! See forum post for details)
-
📦 Pull down new camera test images, rebuild Tags and docs
v21.5.0
-
✨ Added support for ExifTool's MWG Composite Tags. Set the new
ExifToolOptions.useMWGoption totrueto enable. -
✨ Added support for ExifTool's new
ImageDataMD5feature. Set the newExifToolOptions.includeImageDataMD5option totrueto enable. -
📦 Extracted options-related code into modules to remove a couple circular dependencies. Exports should make this transparent to external clients.
v21.4.0
- 🐞 Improved types from
ExifTool.readRaw(). Thanks for the suggestion, Silvio Brändle!
v21.3.0
-
🌱 ExifTool upgraded to v12.60
-
📦 Replaced
Tags.tzSourcemessage"from lat/lon"to"GPSLatitude/GPSLongitude"to be more consistent with other timezone source messages.
v21.2.0
- ✨ Implemented
ExifDateTime.plus(). Added tests.
v21.1.0
-
🐞 Negative GPSLatitude and GPSLongitude values are now supported for EXIF (like
.JPEG),.XMP, and.MIEfiles. Thanks for the bug report, Jason, and the solution, Phil! -
🌱 ExifTool upgraded to v12.56
v21.0.0
-
💔
ExifDateTime.fromDateTime()now takes an option hash as the second argument (instead of the second argument beingrawValue) -
🐞
ExifDateTime.millisecondswill now beundefinedif the EXIF or ISO date string did not specify milliseconds, and will no longer render milliseconds if therawValuedid not include millisecond precision. -
📦 EXIF and ISO dates without specified seconds or milliseconds are now allowed
-
📦 Switched
package.jsonscripts fromyarntonpm, as yarn@1 doesn't work with Node v22.5 and GitHub Actions.
v20.0.0
-
💔
ExifTool.writetook a generic that defaulted toWriteTags, but the type wasn't used for anything. I removed the generic typing, which may require consumers to change their code. -
🌱 ExifTool upgraded to v12.55
-
📦
npm run prettiernow re-organizes imports -
📦 Updated dependencies, re-ran prettier, rebuilt tags, rebuilt docs
v19.0.0
-
💔/🐞 Fix #124: Improved support for filenames with non-latin (a-z0-9) characters on Windows machines that weren't set to UTF-8. Thanks for the bug report and PR, Jürg Rast!
-
💔/🐞 ExifTool v12.54 has several new tags (see the diff) and now renders
GPSAltitudewith negative values when the altitude is below sea level. -
🌱 ExifTool upgraded to v12.54
-
📦 Updated dependencies, re-ran prettier, rebuilt tags, rebuilt docs
-
📦 Node v19 added to the CI test matrix
v18.6.0
-
🌱 ExifTool upgraded to v12.50
-
📦 Updated dependencies, rebuild tags and docs
v18.5.0
-
✨
ExifToolOptionsnow supports anignorableErrorpredicate, used for characterizing errors as "ignorable". Defaults to ignoring the following styles of warnings:Warning: Duplicate MakerNoteUnknown tag in ExifIFDWarning: ICC_Profile deleted. Image colors may be affected
-
🐞 Only read operations are now retried. See #119
v18.4.2
-
🐞 Date-time tags with exactly Common Epoch (
1970-01-01T00:00:00Z) are no longer filtered as invalid. See #118 for details. -
📦 Updated dependencies, rebuild tags and docs
v18.4.1
- 🐞 The public export for
BinaryFieldmistakenly exposed it being namedBinaryDataField. The name of the export and the class are now bothBinaryField.
v18.4.0
-
✨ Binary fields are now parsed to a new
BinaryFieldobject which parses out the length of the binary field -
🐞/📦 Added more required tag fields to
mktags, includingSubSecModifyDate(which fell off of the Tags.ts API in v18.3.0, oops!) -
📦
ExifTimenow retains the raw value to be consistent withExifDateandExifDateTime
v18.3.0
-
🌱 ExifTool upgraded to v12.49, which adds write support to WEBP and a bunch of other goodness
-
📦 Added new cameras to test image corpus, rebuilt tags and docs
-
📦 Updated dependencies
v18.2.0
- ✨ Add support for alternative gps timezone lookup libraries. If you want to use
geo-tzinstead, use something like this:
const geoTz = require("geo-tz");
const { ExifTool } = require("exiftool-vendored");
const exiftool = new ExifTool({
geoToTz: (lat, lon) => geoTz.find(lat, lon)[0],
});
-
✨ If a timezone offset tag is present, and GPS metadata can infer a timezone, and they result in the same offset,
Tags.tzwill use the GPS zone name (likeAmerica/Los_Angeles). -
🐞 We now only apply timezone offset defaults to tag values that are lacking in explicit offsets and are not always encoded in UTC.
-
📦 Timezone "normalization" to a single timezone is no longer applied--if a datetime tag has an offset, the ExifDateTime value should retain that offset value now. Use
ExifDateTime.setZoneif you want to normalize any instance. -
📦 Restore
GPSPositionto the defaultnumericTagsso all GPS lat/lon values are consistent.
v18.1.0
-
📦 Switch from the abandoned
tz-lookuppackage to@photostructure/tz-lookup. Note that this uses an updated time zone geo database, so some time zone names and geo shapes have changed. -
📦 The
GPSPositiontag is no longer included in the default set of numeric tags, as this results in ExifTool returning two floats, whitespace-separated. UseGPSLatitudeandGPSLongitudeinstead.
v18.0.0
-
💔
ReadTask.for()now takes an options hash, which includes the newdefaultVideosToUTCoption. -
🐞 Videos now default to UTC, unless there is a
TimeZone,OffsetTime,OffsetTimeOriginal,OffsetTimeDigitized, orTimeZoneOffsettag value. Thanks for the bug report, @mrbrahman! -
🌱 ExifTool upgraded to v12.45.
v17.1.0
-
✨
ExifDateTimeandExifDatenow have atoMillis()to render in milliseconds from common epoch -
📦 Expose
closeChildProcessesfrom underlying BatchCluster instance -
🐞 Pull in batch-cluster bugfix
(Note that this build does not pull in ExifTool v12.44, due to this bug)
v17.0.1
- 🐞
reasonableTzOffsetMinutes(),extractOffset(), andoffsetMinutesToZoneName()handleUnsetZoneproperly. This shouldn't normally come into play, as this would require serialization of the unset timezone, but... why not, eh?
v17.0.0
-
💔 Luxon has a breaking change. Please verify that date parsing and zone assignments work as expected.
-
🌱 ExifTool upgraded to v12.43.
-
🐞
UnsetZonenow usesInfo.normalizeZone(). -
📦 Updated dependencies
v16.5.1
-
🌱 ExifTool upgraded to v12.42.
-
📦 Updated dependencies
-
📦 Dropped Node v12 from GitHub Actions CI
-
📦 Added RELEASE.md
v16.4.0
-
🐞 Struct values are now properly encoded when writing. Specifically, prior versions didn't support JSON string values (and now WriteTask knows how to serialize those characters to make ExifTool happy)
-
📦/💔
String.htmlEncodewas made private: it was a special-purpose function just forWriteTask. -
📦 Added Node 18 to test matrix. Node 12 will be dropped from support in the next version.
-
📦 Updated dependencies
v16.3.0
-
✨ Added
ExifDateTime.fromMillis() -
📦 Fixed hanging sentence in README. Rebuild docs.
-
📦 Migrated
omit()toObject.
v16.2.0
-
✨ Added read/write support for History and Versions structs.
-
These two tags return typed optional struct arrays.
-
Via the new
StructAppendTagsinterface,ExifTool.write()now accepts plus-suffixed variants of these tags to append to existing records.
-
-
🌱 ExifTool upgraded to v12.41.
-
📦 Updated dependencies
v16.1.0
-
✨ Updated dependencies, including batch-cluster v10.4.0).
This new version will detect when tasks are rejected (due to parsing issues or any other reason), and in that case, the child
exiftoolprocess will be verified to be "healthy" before being put back into the service pool.
v16.0.0
-
💔/🐞 Timezone extraction has been adjusted: if there is a GPS location, we'll prefer that
tzlookupas the authoritative timezone offset. If there isn't GPS lat/lon, we'll useTimezone,OffsetTime, orTimeZoneOffset. If those are missing, we'll infer the offset from UTC offsets.Prior builds would defer to the offset in
Timezone,OffsetTime, orTimeZoneOffset, but GPS is more reliable, and results in a proper time zone (likeAmerica/Los_Angeles). Zone names work correctly even when times are adjusted across daylight savings offset boundaries. -
💔/🐞 Timezone application is now has been improved: if a timezone can be extracted for a given file,
ExifTool.read()will now make allExifDateTimeentries match that timezone. The timestamps should refer to the same timestamp/seconds-from-common-epoch, but "local time" may be different as we've adjusted the timezone accordingly.Metadata sometimes includes a timezone offset, and sometimes it doesn't, and it's all pretty inconsistent, but worse, prior versions would sometimes inherit the current system timezone for an arbitrary subset of tags. This version should remove the system timezone "leaking" into your metadata values.
As an example, if you took a photo with GPS information from Rome (CET, UTC+1), and your computer is in California with
TZ=America/Los_Angeles, prior versions could returnCreateDate: 2022-02-02 02:02:22-07:00. This version will translate that time intoCreateDate: 2022-02-02 11:02:22+01:00.Note that this fix results in
ExifTool.read()rendering differentExifDateTimevalues from prior versions, so I bumped the major version to highlight this change. -
💔
Tagsis automatically generated bymktags, which now has a set of "required" tags with type and group metadata to ensure a core set of tags don't disappear or change types.As a reminder, the
Tagsinterface is only a subset of fields returned, due to TypeScript limitations.ExifTool.read()still returns all values that ExifTool provides. -
🐞 Fixed a bunch of broken API links in the README due to
typedocchanging URLs. Harumph. -
🐞 Prior versions of
ExifDateTime.parseISOwould accept just time or date strings. -
🐞/📦
TimeStamptags may now be properly parsed asExifDateTime. -
📦 Added performance section to the README.
-
📦 Timezone offset formatting changed slightly: the hour offset is no longer zero-padded, which better matches the Luxon implementation we use internally.
-
📦
ExifDateTimecaches the result oftoDateTimenow, which may save a couple extra objects fed to the GC. -
📦 Updated dependencies, including batch-cluster v10.3.2), which fixed several race conditions and added several process performance improvements including support for zero-wait multi-process launches.
v15.12.1
-
📦 Updated dependencies (batch-cluster v10.3.0), including more pessimistic defaults for
streamFlushMillisand newnoTaskDataevent. -
📦 Exported type signatures,
AdditionalWriteTags,ExpandedDateTags,Maybe,Omit, andStructto improvetypedoc-generated documentation. Rebuilt docs.
v15.12.0
-
📦 We now verify external
exiftools are healthy with a-verping every 30 seconds. -
📦 Updated dependencies (batch-cluster v10.2.0) that includes this performance improvement/bugfix
v15.11.0
-
🌱 ExifTool upgraded to v12.40.
-
📦 Updated dependencies (batch-cluster v10.0.0)
-
📦 Rebuild
Tags.tsand docs
v15.10.1
-
📦 Updated dependencies (batch-cluster v8.1.0)
-
📦 Rebuild docs
v15.10.0
v15.9.2
- 📦 Rebuild tags and docs with updated test images. Note that some
GPStags types changed tostring: see v15.8.0.
v15.9.1
- 📦 Exposed
UnsetZoneOffsetMinutesfromTimezones
v15.9.0
- 📦 Exposed
UnsetZoneandUnsetZoneNamefromTimezones
v15.8.0
-
🐞
GPSDateTimein prior versions could be incorrectly parsed, resulting in an incorrectly inferred current-date and encoded-time. -
🐞 GPS latitude and longitude parsing could result in the incorrect hemisphere, depending on the version of ExifTool.
-
📦 The prior default of making all
GPS*tags numeric has been reduced to onlyGPSLatitudeandGPSLongitude, which means tags likeGPSImgDirectionRefwill now be something like "Magnetic North" instead of the more cryptic "M", andGPSAltitudeRefwill now be "Below Sea Level" instead of "1".
v15.7.0
-
🌱 ExifTool upgraded to v12.38.
-
✨ Add specific support for deleting values associated to existing tags
-
🐞 No-op
.write()calls to sidecars are now gracefully no-op'ed. -
📦 Added tests with and without retries (to validate stdout/stderr bugfixes in v8.0 of
batch-cluster) -
📦 Replace
orElsecalls with?? -
📦 Updated dependencies
v15.6.0
-
✨ Added serialization support
-
🌱 ExifTool upgraded to v12.34.
v15.5.0
-
🌱 ExifTool upgraded to v12.33.
-
📦 Updated dependencies
-
📦 Now ignoring
yarn.lock
v15.4.0
-
🌱 ExifTool upgraded to v12.31.
-
📦 Updated dependencies (including new TypeScript, which required import adjustments.
v15.3.0
-
✨
ExifTool.readandExifTool.writenow accept generics. -
🌱 ExifTool upgraded to v12.30.
-
📦 Updated dependencies (including new Luxon and TypeScript)
-
📦 Rebuilt docs
v15.2.0
- 📦 Updated dependencies (including batch-cluster v7.1.0, which fixes a 2s startup delay
v15.1.0
- 📦 Rebuild
Tags.tsfrom more recent exemplars and tag type overrides (v15.0.0 changed toKeywords: string, this version reverts that change)
v15.0.0
-
💔 TypeScript now renders modern (ES2018) JavaScript, which requires a supported version of Node.js.
-
✨ New
ExifTool.extractBinaryTagToBuffer(): extract binary tags directly into aBuffer(watch out for memory bloat from very large binary tag payloads!) -
✨ Expose
ExifTool.childEndCounts(counts of why child processes were recycled: useful for debugging) -
📦 Updated dependencies (including batch-cluster v7.0.0)
v14.6.2
- 📦 Updated batch-cluster (support for listing current tasks)
v14.6.1
- 📦 Updated batch-cluster (support for nullable pids)
v14.6.0
-
🌱 ExifTool upgraded to v12.28.
-
📦 Updated dependencies
v14.5.0
-
🌱 ExifTool upgraded to v12.26.
-
📦 Updated dependencies
v14.4.0
-
✨ Added
ExifDate.rawValue -
📦 Updated dependencies
v14.3.0 🔥
-
🔥/🌱 ExifTool upgraded to v12.25.
All users should upgrade to this version as soon as possible, as this should address CVE-2021-22204.
-
📦 Updated dependencies
v14.2.0
- 🌱 ExifTool upgraded to v12.23
v14.1.1
- 📦 Republish of 14.1.0 (
npfailed to publish 14.1.0 properly)
v14.1.0
-
🌱 ExifTool upgraded to v12.21
-
📦 Stopped excluding sourcemaps
-
📦 Updated dependencies
v14.0.0
-
💔
ExifDateTime.zonewill now return the actual IANA zone name (likeAmerica/Los_Angeles) rather than the time offset. This addresses issues with timezones likeEurope/Kievwhere, from 1900-1924, had an offset ofUTC +2:02:04. -
✨ Added
ExifDateTime.isValid -
🌱 ExifTool upgraded to v12.19
-
📦 Rebuilt Tags.ts and docs
-
📦 Updated dependencies
v13.2.0
-
🌱 ExifTool upgraded to v12.18
-
📦 Updated dependencies
v13.1.0
-
🐞 More complex characters, like emoji that use compound codepoints, like 🦍, 🦄, or 🚵♀️, are now supported. See #87 for more details. Thanks for the report, Gabe Rodriguez!
-
🌱 ExifTool upgraded to v12.14
-
📦 he is now a dependency, which was required by the emoji bugfix.
-
📦 Updated dependencies
v13.0.0
-
💔 The
Tags.tstypes have changed. Some newly-found types were added, many rarely-occurring types have been removed, andTagsub-interfaces have changed. Tag retention heuristics had to be updated, as TypeScript would crash witherror TS2590: Expression produces a union type that is too complex to represent.mktagsnow has a "safe" set of tags that will be retained, and a set of tags that are expressly excluded.These changes won't prevent all type changes from happening in the future, but will prevent these more-common tags from being removed completely.
As several tags are found in several different groups,
mktagsnow tries to place tags first inFileTagsandEXIFTagsgroups before more proprietary APP groups, which should help future interface stability. (This explains whyMIMETypemoved toFileTags, for example). -
🌱 ExifTool upgraded to v12.12.
Note that this version renders file sizes a bit differently: "756 kB" will now be rendered as "756 KiB".
v12.3.1
- 📦 Removed dev dependency on
npm-check-updates, as it no longer supports Node v10 (wth, ncu)
v12.3.0
- 🌱 ExifTool upgraded to v12.10
- 📦 Rebuilt Tags.ts and docs
- 📦 Updated dependencies
v12.2.0
- 🌱 ExifTool upgraded to v12.06
- 📦 Added quoted-file test
v12.1.0
- 🌱 ExifTool upgraded to v12.05
- 📦 Updated dependencies
v12.0.0
- 💔
ExifDateTime.toISOString()now returnsstring | undefined(as it proxies for Luxon'sDateTime.toISO(), which now may returnnull.) - 🌱 ExifTool upgraded to v12.04
- 📦 Rebuilt Tags.ts and docs
- 📦 Updated dependencies
v11.5.0
- 🐞
ExifDateTimeandExifDateno longer accept just a year or year and month. - 📦 Updated dependencies
v11.4.0
- 🌱 ExifTool upgraded to v12.01
- ✨ ExifTool now takes a
Loggerthunk in the constructor options. - 📦 Updated dependencies
v11.3.0
- 🌱 ExifTool upgraded to v11.98
- 📦 BinaryExtractionTasks don't bother retrying when binary payloads are missing (which turns out to be a common issue)
- 📦 ExifToolTask is now exported
- 📦 Updated dependencies
v11.2.0
- 🌱 ExifTool upgraded to v11.95
- 📦 Updated dependencies
v11.1.0
- 📦 Updated dependencies, including
batch-cluster. The newmaxIdleMsPerProcessoption shuts down ExifTool processes automatically if they are idle for longer thanmaxIdleMsPerProcessmilliseconds. New processes are forked when needed.
v11.0.0
- 💔 Breaking change: A number of tags were removed from
Tagsbecause we were getting dangerously close to TypeScript'serror TS2590: Expression produces a union type that is too complex to represent. - 🌱 ExifTool upgraded to v11.93
v10.1.0
- 🐞 ExifTool doesn't (currently) respect
-ignoreMinorErrorswhen extracting binary blobs.BinaryExtractionTasknow assumes stderr messages matching/^warning: /are not actually errors. - 🌱 ExifTool upgraded to v11.92
- 📦 Updated dependencies
- 📦 Prettier 2.0.0 pulled in and codebase reformatted with new defaults, causing huge (no-op) diff.
v10.0.0
- 💔 Breaking change: For the past many major versions, when date and time
fields are invalid, this library returns the raw (invalid) string provided by
ExifTool, rather than an instance of
ExifDateTime,ExifDate, orExifTime. TheTagtypes now reflect this, but you'll probably need to update your code. See #73 for more context. - 🌱 ExifTool upgraded to v11.91
- 📦 Updated dependencies
v9.7.0
- 🐞/✨ Date, DateTime, and Time tags can now ISO formatted. See #71. Thanks for the report, Roland Ayala!
v9.6.0
- 🌱 ExifTool upgraded to v11.86
- 📦 Replace tslint with eslint. Fixed new linting errors.
- 📦 Updated dependencies
v9.5.0
- 🌱 ExifTool upgraded to v11.80
v9.4.0
- 🌱 ExifTool upgraded to v11.78
- 📦 Updated ExifTool's homepage from https://www.sno.phy.queensu.ca/~phil/exiftool/ to https://exiftool.org.
- 📦 Updated dependencies. New
batch-clusterdoesn't propagate errors from ended processes anymore, which should address issue #46.
v9.3.1
- 📦 Updated dependencies. New batch-cluster shouldn't throw errors within async blocks anymore.
v9.3.0
- ✨ Rebuilt
Tagsfrom 8008 example images and videos. New tags were found, but some of the more obscure tags have been dropped. - 🌱 ExifTool upgraded to v11.76
- 📦 Updated dependencies
v9.2.0
- 🌱 ExifTool upgraded to v11.75
- 📦 Updated dependencies, including TypeScript 2.7
v9.1.0
- ✨ Added
ExifTool.deleteAllTags.
v9.0.0
- 📦 This version is using the new Windows packaging of ExifTool written by Oliver Betz, and is why I bumped the major version (as there may be issues with the new packaging).
- 🌱 ExifTool upgraded to v11.73
v8.22.0
- ✨ Added
ExifDateTime.hasZone - ✨
ExifDateTime.toISOStringautomatically omits the timezone offset if unset - 🐞 Hour timezone offsets were rendered without padding (which doesn't comply with the ISO spec).
- 🌱 ExifTool upgraded to v11.65.
v8.21.1
- 🐞 Fixed timezone inference rounding bug (
UTC+2would returnUTC+02:15)
v8.21.0
- ✨ Exposed
Tags.tzSourcefrom.read. This is an optional string holding a description of where and how the source timezone offset,Tags.tz, was extracted. You will love it.
v8.20.0
- ✨ Support for
.ExifTool_configfiles was added. Either place your user configuration file in yourHOMEdirectory, or set theEXIFTOOL_HOMEenvironment variable to the fully-qualified path that contains your user config. Addresses #55.
v8.19.0
- 🌱 ExifTool upgraded to v11.59.
- ✨ Rebuilt
Tagsfrom 6,818 sample images. - 🐞
GPSDateTimeis now forced to beUTC.
v8.18.0
- ✨ Expose
Tags.tzfrom.read. This is an optional string holding the timezone offset, likeUTC+1, or an actual location specification, likeAmerica/Los_Angeles. This is only included when it is specified or inferred from tag values. - ✨ Added another timezone offset extraction heuristic: if
DateTimeUTCand another created-at time is present, the offset is inferred from the delta.
v8.17.0
- ✨ Automagick workaround for AWS Lambda. See the new
ignoreShebangoption, which should automatically be set totrueon non-Windows platforms that don't have/usr/bin/perlinstalled. See #53.
v8.16.0
- 🌱 ExifTool upgraded to v11.55.
v8.15.0
- ✨ Write support has been improved
- Creation of new sidecar files is now supported
- Non-struct list tags (like
Keywords) is now supported - Test coverage includes images,
.XMPfiles, and.MIEfiles
- 📦 Set up
nyc(test coverage report) - 📦 Updated dependencies
v8.14.0
- 🌱 ExifTool upgraded to v11.54.
- 📦 Updated dependencies
- 📦 Mention the need for
perlin the installation instructions. See #51.
v8.13.1
- 📦 Updated dependencies
v8.13.0
- 🐞 Better support for writing tags with date and time values. See #50.
- ✨ Manually added ApplicationRecordTags
- 📦 Updated dependencies
- 📦 Added NodeJS version 12 to the CI build matrix
- 🌱 ExifTool upgraded to v11.51.
v8.12.0
- ✨ Rebuilt
Tagsfrom 6779 examples. New tags were found, includingPreviewTIFF. - 📦 Updated dependencies
- 🌱 ExifTool upgraded to v11.49.
v8.11.0
- 📦 Updated dependencies
- 🌱 ExifTool upgraded to v11.47.
v8.10.1
- 📦 Updated dependencies
v8.10.0
- 🌱 ExifTool upgraded to v11.43.
- 📦 Updated dependencies
v8.9.0
- 🐞 Throw an error if process.platform() returns nullish
- 🌱 ExifTool upgraded to v11.37.
- 📦 Updated dependencies, fixed a couple typing nits
v8.8.0
- 🌱 ExifTool upgraded to v11.34.
- ✨
ExifDateTimeandExifDatenow havefromExifStrictandfromExifLooseparsing methods. - 📦 Updated dependencies
v8.7.1
- 📦 Updated dependencies
- 📦 Moved project to the PhotoStructure github org
v8.7.0
- ✨
ExifDateTimenow has arawValuefield holding the raw value provided byexiftool.
v8.6.1
- 🐞 Luxon 1.12.0 caused issue #46. Fixed ExifDateTime to use new API.
v8.6.0
- 🌱 ExifTool upgraded to v11.32.
- 🐞 Pulled in new batch-cluster
5.6.0,
which fixed an issue with graceful
endpromise resolutions.
v8.5.0
- 🌱 ExifTool upgraded to v11.31.
- 🐞
RewriteAllTagsTaskdoesn't fail on warnings anymore - ✨ Pulled in new batch-cluster
5.4.0,
which fixed
maxProcs.
v8.4.0
- ✨ Pulled in new batch-cluster 5.3.1, which adds support for child start and exit events, internal errors, and more robust result parsing.
- ✨ Rebuilt
Tagsfrom over 6,600 unique camera makes and models. Added new exemplars to ensureKeywords,Title,Subject, and other common user-added tags were included inTags. - ✨ Added tslint, and delinted the codebase. Sparkles because no lint === ✨.
- 📦
WriteTagsnow is a proper superset of values from Tags. - 📦 Updated dependencies
v8.3.0
- 📦 Updated dependencies
- 📦
yarn updatenow usesextract-zip. - 🌱 ExifTool upgraded to v11.29.
v8.2.0
- ✨ Implemented
ExifTool.readRaw. If you decide to use this method, please take care to read the method's documentation. Addresses both #44 and #45.
v8.1.0
- ✨ Added support for EXIF dates that include both the UTC offset as well as the
time zone abbreviation, like
2014:07:17 08:46:27-07:00 DST. The TZA is actually an over-specification, and can be safely discarded. - 🌱 ExifTool upgraded to v11.27.
- 📦 Updated dependencies
- 📦 Mocha 6.0.0 broke
mocha.opts, switched to.mocharc.yaml
v8.0.0
Note that this release supports structures. The value associated to struct
tags will be different from prior versions (in that they will actually be a
structure!). Because of that, I bumped the major version number (but I suspect
most users won't be affected, unless you've been waiting for this feature!)
- 💔 support for structs. Thanks, Joshua Harris!
- 🌱 ExifTool upgraded to v11.26.
- 📦
updatenow requireshttpsfor new ExifTool instance checksums. - 📦 Updated dependencies
v7.6.1
- 🐞 Removed
yyyypadding references that would break under Japanese year eras. Also removed 0 and 1 year validity heuristics.
v7.6.0
- 🌱 ExifTool upgraded to v11.24.
- 🐞 Fix Lat/Lon parsing bug. Thanks, David Randler!
v7.5.0
- 🌱 ExifTool upgraded to v11.21.
v7.4.0
- 🐞
WriteTasknow supports newlines. Fixes #37.
v7.3.0
- 📦 Rebuilt tags using new numeric default for GPS and new smartphone test
images. Note that some tags were incorrect, and have now changed types (like
GPSLatitudeandGPSLongitude). New ExifTool versions gave us a newFlashPixTagsgroup of tags, as well. - 📦 Rebuilt docs
v7.2.1
- 📦 Update dependencies to deal with event-stream 💩🌩️
v7.2.0
- 🌱 ExifTool upgraded to v11.20.
- 🐞
GPS*was added to the default print conversion exceptions. GPS Latitude and Longitude parsing was DRY'ed up, and now ensures correct sign based on Ref. With prior heuristics, if the GPS values were re-encoded without updating ref, the sign would be incorrect. - 🐞 Timezone offset from GPS will be ignored if the date is > 14 hours different
- 📦 added more timezone extraction tests
v7.1.0
- 📦 Moved the date and time parsing into the
ExifDateTime,ExifDate, andExifTimeclasses.
v7.0.1: "nbd it's just the tags"
- 📦 Added more test images to corpus, so there are more tags now.
- 📦 Found error in
Directorytag example, rebuilt tags
v7.0.0: the "time zones & types are hard" edition
-
✨ More robust time zone extraction: this required adding
luxonandtz-lookupas dependencies. See https://photostructure.github.io/exiftool-vendored.js/#dates for more information. -
💔 Tag types are now unions of seen types. Previous typings only included the most prevalent type, which, unfortunately, meant values might return unexpected types at runtime. In an extreme case,
DateTimeOriginalis now correctly reported as beingExifDateTime | ExifTime | number | string, as we return the value from ExifTool if the value is not a valid datetime, date, or time. -
✨ ExifTool's "print conversion" can be disabled for arbitrary tags, and the defaults include
Orientationand*Duration*(note that globs are supported!).By default, ExifTool-Vendored versions prior to
7.0.0used ExifTool's print conversion code for most numeric values, rather than the actual numeric value. While ExifTool's output is reasonable for humans, writing code that consumed those values turned out to be hacky and brittle. -
🐞 Depending on OS, errors might not be correctly reported. This issue was from
batch-cluster, whose version 5.0.0 fixed this problem, and was pulled into this release. -
🌱 ExifTool upgraded to v11.15.
v6.3.0
- 🌱 ExifTool upgraded to v11.13.
- ✨ Rebuilt
Tagsbased on new phone and camera models
v6.2.3
- 📦 Better tag ratings by rebuilding tags with ExifTool's default category sorting. This fixed a number of tags (like ExposureTime, ISO, and FNumber) that were erroneously marked as "rare" because they were also (rarely) found in APP categories.
v6.2.2
- 🐞 Increased default task timeout to 20s to resolve #34
v6.2.1
- 📦 Pull in batch-cluster 4.3.0, which exposes
taskDataevents.
v6.2.0
- ✨/🐞 Joshua Harris added support for writing arrays
- 🌱 ExifTool upgraded to v11.10.
v6.1.2
- 📦 By pulling in the latest batch-cluster, the default logger is NoLogger, which may be a nicer default for people. Added logging, event, and error information to the README.
v6.1.1
- 🐞 Warnings work now, and I even have a test to prove it. 😳
- ✨ Warning-vs-fatal errors can be configured via the new
minorErrorsRegExpconstructor parameter, or if you need more flexibility, by providing arejectTaskOnStderrimplementation to the ExifTool constructor.
v6.1.0
- ✨ Warnings are back! Non-fatal processing errors are added to the Tags.errors field.
- 📦 Pulled in new typedoc version and switched to "file" rendering, which seems to generate better docs. This unfortunately broke links to underlying jsdocs.
v6.0.1
- 📦 Typedoc fails to render
Partial<>composites, somktagsnow renders each Tag as optional. TheTaginterface should be exactly the same as from v6.0.0.
v6.0.0
- 💔
ExifTool's many constructor parameters turned out to be quite unwieldy. 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.enqueueTasktakes 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
Tagsbased 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 onENOENT, 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
runningfunction has changed to return aPromise<number[]>. - 🌱 ExifTool upgraded to v11.09.
v5.5.0
- 🌱 ExifTool upgraded to v11.08.
v5.4.0
- ✨ Some photo sharing sites will set the
CreateDateorSubSecCreateDateto invalid values like0001:01:01 00:00:00.00. These values are now returned as strings so consumers can more consistently discriminate invalid metadata.
v5.3.0
-
✨ Prior versions of
ExifTool.read()always added the-fastoption. This read mode omits metadata found after the image payload. This makes reads much faster, but means that a few tags, likeOriginalImageHeight, 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
-fasta user preference. To maintain existing behavior, I've made the optional second argument ofExifTool.readdefault to["-fast"]. If you want to use "slow mode", just give an empty array to the second argument. If you want-fast2mode, provide["-fast2"]as the second argument.
v5.2.0
- 🌱 ExifTool upgraded to v11.06.
- 📦 Removed node 9 from the build graph, as it isn't supported anymore: https://github.com/nodejs/Release#release-schedule
- 📦 Pull in latest dependencies
v5.1.0
- ✨ new
exiftool.rewriteAllTags(), which may repair problematic image metadata. - 🌱 ExifTool upgraded to v11.02.
- 📦 taskRetries default is now 1, which should allow recovery of the rare RPC/fork error, but actual corrupt files and real errors can be rejected sooner.
- 📦 Pull in latest dependencies, include new batch-cluster.
v5.0.0
- 💔/✨ Task rejections are always
Errors now, andExifTool.onobservers 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
- 🌱 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
- 🌱 ExifTool upgraded to v10.98
v4.24.0
- 🌱 ExifTool upgraded to v10.95
- 📦 Fix
.pldependency to omit test files and documentation
v4.23.0
- 🌱 ExifTool upgraded to v10.94
- 📦 Pull in latest dependencies, including more robust BatchCluster exiting (which may help with rare child zombies during long-lived parent processes on macOS)
v4.22.1
- 📦 Pull in latest dependencies, including less-verbose BatchCluster
v4.22.0
v4.21.0
- ✨ Before reading or writing tags, we stat the file first to ensure it exists.
Expect
ENOENTrejections fromExifTool.readandExifTool.writenow. - 📦 Expose batch-cluster lifecycle events and logger
- 🌱 ExifTool upgraded to v10.92
v4.20.0
- ✨ Support for Electron. Added
exiftoolPathto theExifToolconstructor. See the wiki for more information. - 🌱 ExifTool upgraded to v10.89
v4.19.0
- 🌱 ExifTool upgraded to v10.86
v4.18.1
- 📦 Pick up batch-cluster 1.10.0 to possibly address this issue.
v4.18.0
- 🌱 ExifTool upgraded to v10.81
- 📦 Update deps, including batch-cluster 1.9.0
- 📦 Dropped support for node 4 (EOLs in 1 month).
v4.17.0
v4.16.0
- 🌱 ExifTool upgraded to v10.78
- 📦 Update deps, including TypeScript 2.7.1
v4.15.0
- 🌱 ExifTool upgraded to v10.76
- 📦 Update deps
v4.14.1
- 📦 Update deps
v4.14.0
- 🐞 Use
spawninstead ofexecFile, as the latter has buggymaxBufferexit behavior and could leak exiftool processes on windows - 🐞 The
.exiftoolsingleton now properly uses aDefaultMaxProcsconst.
v4.13.1
- 🌱 ExifTool upgraded to v10.70
- 📦 Replace
tslintandtsfmtwithprettier - 📦 Add test coverage report
(due to buggy interactions between yarn and np, v4.13.0 was published in
an incomplete state and subsequently unpublished)
v4.12.1
- 📦 Rollback the rollback, as it's a known issue with par. If this happens again I'll add a windows-specific validation of the par directory.
v4.12.0
- 🐞 Rollback to ExifTool v10.65 to avoid this windows issue
v4.11.0
- ✨ Support for non-latin filenames and tag values Thanks, Demiurga!
v4.10.0
- 🌱 ExifTool upgraded to v10.67
v4.9.2
- 📦 More conservative default for
maxProcs:Math.max(1, system cpus / 4).
v4.9.0
- 📦 Expose
ExifTool.ended
v4.8.0
- ✨ Corrected the type interface to
ExifTool.write()to be only string or numeric values with keys fromTagsso intellisense can work it's magicks - 📦 Updated the README with more examples
- 📦 Added timestamp write tests
v4.7.1
- ✨ Metadata writing is now supported. Closes #6
v4.6.0
- 🌱 ExifTool upgraded to v10.66
- ✨ Pull in new
batch-clusterwith more aggressive child process management (usestaskkillon win32 platforms andkill -9on unix-ish platforms) - ✨ ExifTool constructor defaults were relaxed to handle slow NAS
- ✨ Upgraded to Mocha 4.0. Added calls to
exiftool.end()in testafterblocks and the README so--exitisn't necessary. - 📦 Upgraded all dependencies
v4.5.0
- 🌱 ExifTool upgraded to v10.64
v4.4.1
- 📦 reverted batch-cluster reference
v4.4.0
- 🌱 ExifTool upgraded to v10.61
- 🐞 Re-added the "-stay_open\nFalse" ExifTool exit command, which may be more reliable than only using signal traps.
- 📦
yarn upgrade --latest
v4.3.0
- 🌱 ExifTool upgraded to v10.60
- 📦 Upgraded all dependencies
v4.2.0
- 🌱 ExifTool upgraded to v10.58
v4.1.0
- 📦 Added
QuickTimeTagsfrom several example movies (previous versions ofTagsdidn't have movie tag exemplar values) - 🌱 ExifTool upgraded to v10.57
v4.0.0
- 💔 All
Tagsfields are now marked as possibly undefined, as there are no EXIF, IPTC, or other values that are guaranteed to be set. Sorry for the major break, but the prior signature that promised all values were always set was strictly wrong. - ✨ Added support for all downstream batch-cluster options in the ExifTool constructor.
- 📦 Added
ExifTool.pids(used by a couple new integration tests) - 📦 Rebuilt
Tagswith additional sample images and looser tag filtering.
v3.2.0
- 🌱 ExifTool upgraded to v10.54
- 📦 Pulled in batch-cluster v1.2.0 that supports more robust child process cleanup
- ✨ Yarn and
platform-dependent-modulesdon't play nicely. Anton Mokrushin submitted several PRs to address this. Thanks!
v3.1.1
- 🐞 Fixed
package.jsonreferences totypesandmain
v3.1.0
- 📦 Completed jsdocs for ExifTool constructor
- 📦 Pulled in batch-cluster v1.1.0 that adds both
on("beforeExit")andon("exit")handlers
v3.0.0
- ✨ Extracted batch-cluster to power child process management. Task timeout, retry, and failure handling has excellent test coverage now.
- 💔 Switched from debug to node's debuglog to reduce external dependencies
- 🌱 ExifTool upgraded to v10.51
- 📦 Using
.npmignoreinstead of package.json'sfilesdirective to specify the contents of the module.
v2.17.1
- 🐛 Rounded milliseconds were not set by
ExifDateTime.toDate()when timezone was not available. Breaking tests were added.
v2.16.1
- 📦 Exposed datetime parsing via static methods on
ExifDateTime,ExifDate, andExifTime.
v2.16.0
- ✨ Some newer smartphones (like the Google Pixel) render timestamps with microsecond precision, which is now supported.
v2.15.0
- ✨ Added example movies to the sample image corpus used to build the tag definitions.
v2.14.0
- ✨ Added
taskTimeoutMillis, which will cause the promise to be rejected if exiftool takes longer than this value to parse the file. Note that this timeout only starts "ticking" when the task is enqueued to an idle ExifTool process. - ✨ Pump the
onIdlemethod everyonIdleIntervalMillis(defaults to every 10 seconds) to ensure all requested tasks are serviced. - ✨ If
ECONNorECONNRESETis raised from the child process (which seems to happen for roughly 1% of requests), the current task is re-enqueued and the current exiftool process is recycled. - ✨ Rebuilt
Tagsdefinitions using more (6,412!) sample image files (vianpm run mktags ~/sample-images), including many RAW image types (like.ORF,.CR2, and.NEF).
v2.13.0
- ✨ Added
maxReusesbefore exiftool processes are recycled - 🌱 ExifTool upgraded to v10.50
v2.12.0
- 🐛 Fixed
gps.toDate is not a function
v2.11.0
- 🌱 ExifTool upgraded to v10.47
- ✨ Added call to
.kill()on.end()in case the stdin command was missed by ExifTool
v2.10.0
- ✨ Added support for Node 4. TypeScript builds under es5 mode.
v2.9.0
- 🌱 ExifTool upgraded to v10.46
v2.8.0
- 🌱 ExifTool upgraded to v10.44
- 📦 Upgraded to TypeScript 2.2
- 🐞
update/io.tserror message didn't handle null statuscodes properly - 🐞
update/mktags.tshad a counting bug exposed by TS 2.2
v2.7.0
- ✨ More robust error handling for child processes (previously there was no
.on("error")added to the process itself, only onstderrof the child process).
v2.6.0
- 🌱 ExifTool upgraded to v10.41
- ✨
Orientationis rendered as a string by ExifTool, which was surprising (to me, at least). By exposing optional args inExifTool.read, the caller can choose how ExifTool renders tag values.
v2.5.0
- 🐞
LANGandLC_environment variables were passed through to exiftool (and subsequently, perl). These are now explicitly unset when exec'ing ExifTool, both to ensure tag names aren't internationalized, and to prevent perl errors from bubbling up to the caller due to missing locales.
v2.4.0
- ✨
extractBinaryTagexposed because there are a lot of binary tags (and they aren't all embedded images) - 🐞
JpgFromRawwas missing inTag(no raw images were in the example corpus!)
v2.3.0
- ✨
extractJpgFromRawimplemented to pull out EXIF-embedded images from RAW formats
v2.2.0
- 🌱 ExifTool upgraded to v10.40
v2.1.1
- ✨
extractThumbnailandextractPreviewimplemented to pull out EXIF-embedded images - 📦 Rebuilt package.json.files section
v2.0.1
- 💔 Switched from home-grown
loggerto debug
v1.5.3
- 📦 Switch back to
platform-dependent-modules. npm warnings aren't awesome. - 📦 Don't include tests or updater in the published package
v1.5.0
- 🌱 ExifTool upgraded to v10.38
- 📦 Use
npm's os-specific optionalDependencies rather thanplatform-dependent-modules.
v1.4.1
- 🐛 Several imports (like
process) name-collided on the globals imported by Electron
v1.4.0
- 🌱 ExifTool upgraded to v10.37
v1.3.0
- 🌱 ExifTool upgraded to v10.36
- ✨
Tag.Errorexposed for unsupported file types.
v1.2.0
- 🐛 It was too easy to miss calling
ExifTool.end(), which left child ExifTool processes running. The constructor to ExifTool now adds a shutdown hook to send all child processes a shutdown signal.
v1.1.0
- ✨ Added
toString()for all date/time types
v1.0.0
- ✨ Added typings reference in the package.json
- 🌱 Upgraded vendored exiftool to 10.33
v0.4.0
- 📦 Fixed packaging (maintain jsdocs in .d.ts and added typings reference)
- 📦 Using np for packaging
v0.3.0
- ✨ Multithreading support with the
maxProcsctor param - ✨ Added tests for reading images with truncated or missing EXIF headers
- ✨ Added tests for timezone offset extraction and rendering
- ✨ Subsecond resolution from the Google Pixel has 8 significant digits(!!), added support for that.
v0.2.0
- ✨ More rigorous TimeZone extraction from assets, and added the
ExifTimeZoneOffsetto handle theTimeZonecomposite tag - ✨ Added support for millisecond timestamps
v0.1.1
🌱✨ Initial Release. Packages ExifTool v10.31.