Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

composite-symbol logo, showing the Unicode character "Composition Symbol": the overlapping outlines of a square and a circle

Composite Symbol

Get a unique JavaScript Symbol from a series of values, inspired by Bradley Farias' Richer Keys proposal.

JavaScript Style Guide Tests npm

The Problem

Since ES2015, we can use arbitrary objects as dictionay keys by using Maps.

However, sometimes we need to map data to not just one object but to multiple values, for example to attach data to relationships. JavaScript unfortunately has no built-in way for this.

A Solution

This package provides a getCompositeSymbol function which takes an arbitrary (non-zero) number of values and returns a unique Symbol. Whenever the same series of values is passed to getCompositeSymbol, the same Symbol is going to be returned.

These unique Symbols allow us to construct things around them, e.g. we could use them as keys in dictionaries.


We can use this feature to attach metadata to a relationship between two objects, without having to tack it onto the participating objects themselves:

const getCompositeSymbol = require('composite-symbol')

// Imaginary models
const Person = require('person')
const { Prius, Ferrari } = require('cars')

// We want to store information about how people use their cars
const carRelationships = {}

// Say hi to John!
const john = new Person()

// John owns an old Toyota Prius = new Prius()

// John needs his car to drive to work everyday
carRelationships[getCompositeSymbol(john, 'car')] = 'drives to work daily'

// How about John buying a new car? He really earned it. = new Ferrari()

// But John still needs to drive to work everyday
carRelationships[getCompositeSymbol(john, 'car')] // === "drives to work daily"


Install it from npm:

npm install --save composite-symbol


  • Order matters! getCompositeSymbol(1, 2, 3) will not return the same symbol as getCompositeSymbol(3, 2, 1).
  • Symbols are not unique across realms. That means, getCompositeSymbol(1, 2, 3) in browser window A will not return the same symbol as getCompositeSymbol(1, 2, 3) in browser window B.
  • Symbols, as well as Maps (which this package uses in the background) are ES2015 features. This is not a problem in Node.js anymore, but if you want to use this package in the browser, be aware that it will not work in Internet Explorer.


✳️ Map a series of values to a unique JavaScript Symbol







No packages published

Contributors 4