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

js-emoji-fork

v1.0.0

Published

A JS Emoji conversion library

Downloads

4

Readme

js-emoji - Display emoji in the browser, everywhere

Build Status Coverage Status

Recent OSX and iOS versions allow display and input of emoji. It's nice to show them on other devices too, and the browser is a good place to do it. This library converts emoji (either from character codes or colon-sequences like :smile:) into something that will work on the host computer - either native character codes, a CSS styled span or a text representation.

Usage

<link href="emoji.css" rel="stylesheet" type="text/css" />
<script src="emoji.js" type="text/javascript"></script>
<script type="text/javascript">

// replaces \u{1F604} with platform appropriate content
var output1 = emoji.replace_unified(input);

// replaces :smile: with platform appropriate content
var output2 = emoji.replace_colons(input);

// force text output mode
emoji.text_mode = true;

// show the short-name as a `title` attribute for css/img emoji
emoji.include_title = true;

// change the path to your emoji images (requires trailing slash)
// you can grab the images from here:
// https://github.com/github/gemoji/tree/master/images/emoji/unicode
emoji.img_path = "http://my-cdn.com/images/emoji/";

// find out the auto-detected mode
alert(emoji.replace_mode);

</script>

You can view a live demo here.

Lifecycle

The library is designed to be used with the following flow:

  1. User enters text on an iPhone/iPod, Mac running OSX Lion or Android phone
  2. Within that text, user enters some emoji
  3. Data is stored by application, optionally translated to :colon: style
  4. When data is viewed by users on iPhone, Lion Mac or Android phone, emoji appear normally
  5. When data is viewed on PC, older Mac or Linux, emoji are replaced with inline <span> elements with background images or simple images.

While the JS library can replace unified emoji codes (as used by iOS6), it's much slower than replacing colon sequences. By translating to and storing colon sequences on the backend, you are able to:

  • Support Android phones (Google emoji codepoints)
  • Support older iPhones (Softbank emoji codepoints)
  • Allow PC users to enter :smile: and have it appear as an emoji everywhere

Using MySQL for storage

Some special care may be needed to store emoji in your database. While some characters (e.g. Cloud, U+2601) are within the Basic Multilingual Plane (BMP), others (e.g. Close Umbrella, U+1F302) are not. As such, they require 4 bytes of storage to encode each character. Inside MySQL, this requires switching from utf8 storage to utf8mb4.

You can modify a database and table using a statement like:

ALTER DATABASE my_database DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
ALTER TABLE my_table CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;

You will also need to modify your connection character set.

You don't need to worry about this if you translate to colon syntax before storage.