node-vibrant

Extract prominent colors from an image.

This project is refactored into a monorepo in version 3.2.0 (see develop branch, npm version node-vibrant@3.2.0-alpha).

We will not merge new PRs to v3.1 related to new featuresets during this time. However, bug fixes and security vulnerability fixes are still highly encouraged.

Quantization is the most time-consuming stage in node-vibrant. In v3.0, the quantization can be run in the WebWorker to avoid freezing the UI thread.

Here's how to use this feature:

1. Use WebWorker build dist/vibrant.worker.js or dist/vibrant.worker.min.js. Or if you are re-bundling with webpack, use lib/bundle.worker.js as entry
2. Use WebWorker quantizer:

   let v = Vibrant.from(src)
     .useQuantizer(Vibrant.Quantizer.WebWorker)
     // Other configurations

• Identical API for both node.js and browser environment
• Support browserify/webpack
• Consistent results (*See Result Consistency)

$ npm install node-vibrant

// ES5
var Vibrant = require('node-vibrant')
// ES6
import * as Vibrant from 'node-vibrant'
// TypeScript
import Vibrant = require('node-vibrant')

// Using builder
Vibrant.from('path/to/image').getPalette((err, palette) => console.log(palette))
// Promise
Vibrant.from('path/to/image').getPalette()
  .then((palette) => console.log(palette))

// Using constructor
let v = new Vibrant('path/to/image', opts)
v.getPalette((err, palette) => console.log(palette))
// Promise
v.getPalette().then((palette) => console.log(palette))

If you installed node-vibrant with npm, compiled bundles are available under node_modules/node-vibrant/dist. Or you can download bundles from Relases.

<!-- Debug version -->
<script src="/path/to/dist/vibrant.js"></script>
<!-- Uglified version -->
<script src="/path/to/dist/vibrant.min.js"></script>

<script>
  // Use `Vibrant` in script
  // Vibrant is exported to global. window.Vibrant === Vibrant
  Vibrant.from('path/to/image').getPalette(function(err, palette) {});
  // Promise
  Vibrant.from('path/to/image').getPalette().then(function(palette) {});
  // Or
  var v = new Vibrant('/path/to/image', opts);
  // ... same as in node.js
</script>

1. Make changes
2. Write test specs if necessary
3. Pass tests
4. Commit source files only (without compiled files)

Main class of node-vibrant.

Make a Builder for an image. Returns a Builder instance.

export type ImageSource = string
  | HTMLImageElement  // Browser only
  | Buffer            // Node.js only

export interface Options {
    colorCount: number
    quality: number
    maxDimension: number
    filters: Array<Filter>
    ImageClass: ImageClass
    quantizer: Quantizer
    generator?: Generator
}

export type Resolvable<T> = T | Promise<T>

export interface Quantizer {
    (pixels: Pixels, opts: Options): Resolvable<Array<Swatch>>
}

export interface Generator {
    (swatches: Array<Swatch>, opts?: Object): Resolvable<Palette>
}

Returns true if the color is to be kept.

export interface Filter {
    (red: number, green: number, blue: number, alpha: number): boolean
}

export interface Callback<T> {
    (err?: Error, result?: T): void
}

Alias of getPalette.

Helper class for change configurations and create a Vibrant instance. Methods of a Builder instance can be chained like:

Vibrant.from(src)
  .quality(1)
  .clearFilters()
  // ...
  .getPalette()
  .then((palette) => {})

Arguments are the same as Vibrant.constructor.

Sets opts.quality to q. Returns this Builder instance.

Sets opts.colorCount to n. Returns this Builder instance.

Sets opts.maxDimension to d. Returns this Builder instance.

Adds a filter function. Returns this Builder instance.

Removes a filter function. Returns this Builder instance.

Clear all filters. Returns this Builder instance.

Specifies which Image implementation class to use. Returns this Builder instance.

Specifies which Quantizer implementation class to use. Returns this Builder instance.

Sets opts.generator to generator. Returns this Builder instance.

Builds and returns a Vibrant instance as configured.

Builds a Vibrant instance as configured and calls its getPalette method.

Alias of getPalette.

Represents a color swatch generated from an image's palette.

export interface Vec3 extends Array<number> {
    0: number,
    1: number,
    2: number
}

Internal use.

Returns an appropriate color to use for any 'title' text which is displayed over this Swatch's color.

Returns an appropriate color to use for any 'body' text which is displayed over this Swatch's color.

Utility methods. Internal usage.

Computes CIE delta E 1994 diff between lab1 and lab2. The 2 colors are in CIE-Lab color space. Used in tests to compare 2 colors' perceptual similarity.

Compute CIE delta E 1994 diff between rgb1 and rgb2.

Compute CIE delta E 1994 diff between hex1 and hex2.

Gets a string to describe the meaning of the color diff. Used in tests.

• node-vibrant takes image path, not the image object as parameter for the obvious reason that node.js environment has no access to HTML DOM object.
• node-vibrant provides asynchronous API since most node.js image processing library is asynchronous. And the original vibrant.js workflow is asynchronous any way (though you will have to handle the image loading yourself, while node-vibrant does it for you).
• node-vibrant uses one single opts object to hold all options for future expansions. And it feels more node.js-like.
• node-vibrant uses method call to initiate image processing instead of constructor so that developers can use it with Promise.

The results is consistent within each user's browser instance regardelss of visible region or display size of the image, unlike the original vibrant.js implementation.

However, due to the very nature of HTML5 canvas element, image rendering is platform/machine-dependent. Thus the resulting swatches in browser environment varies and may not be the same as in node.js nor in another machine. See Canvas Fingerprinting.

The test specs use CIE delta E 1994 color difference to measure inconsistencies across platforms. It compares the generated color on node.js, Chrome, Firefox and IE11. At quality == 1 (no downsampling) and no filters, the results are rather consistent. Color diffs between browsers are mostly not perceptible by human eyes. Downsampling will cause perceptible inconsistent results across browsers due to differences in canvas implementations.