Usage

npm i @emoji-platform-data/windows

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

console.log(byEmoji["😂"]);
/*
{
	emoji: "😂",
	keywords: ["crying", "face", "feels", "funny", "haha", "happy", "hehe", "hilarious", "joy", "laugh", "lmao", "lol", "rofl", ...],
	name: "face with tears of joy",
}
*/

• 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 WindowsItem describing one emoji as the Windows emoji panel -the one Win + . opens- knows it:

• name is how Windows names the emoji, close to its Unicode CLDR name, such as octopus for 🐙.
• keywords are the other terms the panel searches, from CLDR's annotations to slang and emoticons, such as ttyl for 👋 and :-o for 😲: nearly every emoji has them.

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 panel's own en-US data from the newest retail Windows 11 release, with far more keywords than the Fluent UI metadata in @emoji-platform-data/fluemoji, and DEVELOPMENT.md explains how to refresh it.

Skin tone combinations of emoji showing more than one person, such as 🫱🏻‍🫲🏼, are left out since they only add skin tone names to their base emoji's keywords.

The panel's categories and order aren't here, since they're part of the panel itself rather than this data.

The names and keywords are Microsoft's: this package's MIT license only covers the code that packages them, and this package includes no Windows emoji artwork.