Usage

npm i @emoji-platform-data/discord

import { byEmoji, byTitle } from "@emoji-platform-data/discord";

console.log(byEmoji["👍"]);
/*
{
	aliases: ["+1", "thumbup", "thumbs_up"],
	category: "people",
	emoji: "👍",
	keywords: ["+1", "good", "hand", "like", "thumb", "up", "yes"],
	name: "thumbsup",
	order: 134,
	unicodeVersion: 6,
}
*/

• byEmoji takes a glyph as any platform writes it, with or without its U+FE0F: byEmoji["⚓️"] and byEmoji["⚓"] are the same entry.
• byTitle takes a PascalCase Emojipedia title.

Each entry is a DiscordItem describing one emoji as Discord's own emoji picker knows it:

• name is the shortcode Discord writes the emoji as, and aliases are the others it accepts.
• keywords are the picker's other search terms, such as celebrate for 🎉 (tada): country flags, keycaps, regional indicators, and some sequences, such as most families, have none.
• order is the emoji's position in the picker, across all categories.

This package is only static JSON and types, with no runtime dependencies, and its data is also in the combined emoji-platform-data.

Where This Data Comes From

This is a snapshot of the emoji data in Discord's web client JavaScript bundle, with its en-US keywords, and DEVELOPMENT.md explains how to refresh it.

Skin tone variants, such as wave_tone3, are left out since they have no terms of their own.

The shortcodes, keywords, categories, and ordering are Discord's: this package's MIT license only covers the code that packages them, and this package includes no Discord emoji artwork.