sharp

@param 'images': Array<string|Buffer>|string|Buffer → string | Buffer<ArrayBufferLike> | (string | Buffer<Array.... Types differ. Run with --fix to update JSDoc, or verify the intended type.

@param 'images': Object[] → { input?: string | Buffer<ArrayBufferLike>; }[]. JSDoc declares array but TypeScript infers union.

@returns: Promise<Object> → Promise<any>. Types differ. Run with --fix to update JSDoc, or verify the intended type.

@param 'options': Object → { background?: any; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { background?: any; idx?: number; idy?: number; odx?: num.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { background?: any; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { alpha?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { lower?: number; upper?: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { lower?: number; upper?: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { width: number; height: number; maxSlope?: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'kernel': Object → { width: number; height: number; kernel: number[]; scale?.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { greyscale?: boolean; grayscale?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { raw?: { width?: number; height?: number; channels?: num.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { brightness?: number; saturation?: number; hue?: number;.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@returns: Promise<Object> → Promise<any>. Types differ. Run with --fix to update JSDoc, or verify the intended type.

@param 'options': Object → { resolveWithObject?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'exif': Object<string, Object<string, string>> → { [x: string]: { [x: string]: string; }; }. JSDoc declares generic but TypeScript infers object.

@param 'exif': Object<string, Object<string, string>> → { [x: string]: { [x: string]: string; }; }. JSDoc declares generic but TypeScript infers object.

@param 'options': Object → { attach?: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { orientation?: number; density?: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { quality?: number; progressive?: boolean; chromaSubsampl.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { progressive?: boolean; compressionLevel?: number; adapt.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { quality?: number; alphaQuality?: number; lossless?: boo.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { reuse?: boolean; progressive?: boolean; colours?: numbe.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { quality?: number; lossless?: boolean; tileWidth?: numbe.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'source': Object → { loop?: number; delay?: number[]; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { quality?: number; force?: boolean; compression?: string.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { quality?: number; lossless?: boolean; effort?: number; .... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { compression: string; quality?: number; lossless?: boole.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { distance?: number; quality?: number; decodingTier?: num.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { depth?: string; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { size?: number; overlap?: number; angle?: number; backgr.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { seconds: number; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { force?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { width?: number; height?: number; fit?: string; position.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { left: number; top: number; width: number; height: numbe.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { background?: any; threshold?: number; lineArt?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { operation: string[]; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { operation: string[]; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.