Skip to content

maxMemoryUsageInMB - dependency of jimp/plugin-resize #144

Open
@twofingerrightclick

Description

@twofingerrightclick

When trying to get palettes from larger images (like jpegs greater than 5mb) (using node) it appears that jimp/plugin-resize throws a maxMemoryUsageInMB error. The default for jimp decode options is 512mb.

Where can it be configured from node-vibrant to allow working with larger images?

Be neat if the Jimp object could be exposed by Vibrant allowing for configuration like so:
Jimp.decoders['image/jpeg'] = (data: Buffer) => JPEG.decode(data, { maxMemoryUsageInMB: 1024 });

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions