New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

exiftool-vendored

Package Overview
Dependencies
Maintainers
1
Versions
252
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

exiftool-vendored - npm Package Compare versions

Comparing version 3.1.0 to 3.1.1

6

CHANGELOG.md

@@ -25,4 +25,8 @@ ## Versioning

### v3.0.1
### v3.1.1
* 🐞 Fixed `package.json` references to `types` and `main`
### v3.1.0
* 📦 Completed jsdocs for ExifTool constructor

@@ -29,0 +33,0 @@ * 📦 Pulled in batch-cluster v1.1.0 that adds both `on("beforeExit")` and

9

dist/ExifTool.d.ts

@@ -100,7 +100,10 @@ import { ExifToolTask } from "./ExifToolTask";

/**
* Use this singleton rather than instantiating new ExifTool instances
* in order to leverage a single running ExifTool process.
* Use this singleton rather than instantiating new ExifTool instances in order
* to leverage a single running ExifTool process. As of v3.0, its `maxProcs` is
* set to the number of CPUs on the current system; no more than `maxProcs`
* instances of `exiftool` will be spawned.
*
* Note that this instance will only use 1 CPU.
* Note that each child process consumes between 10 and 50 MB of RAM. If you
* have limited system resources you may want to use a smaller `maxProcs` value.
*/
export declare const exiftool: ExifTool;

@@ -9,2 +9,3 @@ "use strict";

var _fs = require("fs");
var _os = require("os");
var _process = require("process");

@@ -159,8 +160,11 @@ var DateTime_1 = require("./DateTime");

/**
* Use this singleton rather than instantiating new ExifTool instances
* in order to leverage a single running ExifTool process.
* Use this singleton rather than instantiating new ExifTool instances in order
* to leverage a single running ExifTool process. As of v3.0, its `maxProcs` is
* set to the number of CPUs on the current system; no more than `maxProcs`
* instances of `exiftool` will be spawned.
*
* Note that this instance will only use 1 CPU.
* Note that each child process consumes between 10 and 50 MB of RAM. If you
* have limited system resources you may want to use a smaller `maxProcs` value.
*/
exports.exiftool = new ExifTool();
exports.exiftool = new ExifTool(_os.cpus().length);
//# sourceMappingURL=ExifTool.js.map
{
"name": "exiftool-vendored",
"version": "3.1.0",
"version": "3.1.1",
"description": "Efficient, cross-platform access to ExifTool",
"main": "./dist/exiftool.js",
"types": "./dist/exiftool.d.ts",
"main": "./dist/ExifTool.js",
"types": "./dist/ExifTool.d.ts",
"scripts": {

@@ -8,0 +8,0 @@ "clean": "rimraf lib dist",

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc