npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

emoji-metadata

v1.0.1

Published

metadata for emoji scraped from the unicode.org page

Downloads

10

Readme

Emoji Metadata

The best source of truth for emoji is the Unicode.org text file.

The data is obtained via the update script (updata-from-source.mjs).

Changes from v1.0

Instead of main being set to emoji-metadata.json it is now set to the lighter-weight emoji.js.

Only fully-qualified emoji are included.

Four versions of the data are provided (and it should be easy to add more):

emoji.js

This is a simple array of emoji provided as an ES6 module.

Usage:

import emoji from 'emoji-metadata'

The data looks like this:

export default [
  {
    category: "Smileys & Emotion",
    subcategory: "face-smiling",
    chars: "😀",
    name: "grinning face"
  },
  {
    category: "Smileys & Emotion",
    subcategory: "face-smiling",
    chars: "😃",
    name: "grinning face with big eyes"
  },
  ...
]

emoji-groups.json

This is a hierarchical structure of groups and subgroups.

It looks like this:

[
  {
    "name": "Smileys & Emotion",
    "subGroups": [
      {
        "name": "face-smiling",
        "emoji": [
          {
            "codes": [
              "U+1F600"
            ],
            "chars": "😀",
            "name": "grinning face"
          },
          ...
        ]
      },
      ...
    ],
  },
  ...
]

emoji-metadata.json

This is the same data as emoji-groups, but flattened.

It looks like this:

[
  {
    "category": "Smileys & Emotion",
    "subcategory": "face-smiling",
    "codes": [
      "U+1F600"
    ],
    "chars": "😀",
    "name": "grinning face"
  },
  {
    "category": "Smileys & Emotion",
    "subcategory": "face-smiling",
    "codes": [
      "U+1F603"
    ],
    "chars": "😃",
    "name": "grinning face with big eyes"
  },
  ...
]

The javascript version is obviously the most convenient to use. The hierarchical version is the most efficient (unless you don't want the codes), while emoji-metadata strikes a happy medium (and with on-the-fly compression is probably hardly larger than the hierarchical version).

Finally, the version of the unicode data is stored in emoji-version.json in case that's helpful.