Security News
Bun 1.2 Released with 90% Node.js Compatibility and Built-in S3 Object Support
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
In a given string convert unicode and :shortcode:
emojis to <img />
tags.
Currently supported Unicode version: 11.0
. Minimum supported emojione-assets
version: 4.0.0
.
This package is a collection of utility functions loosely based to twemoji
and emojione
javascript libraries. It aims to completely replace those with a modern ES implementation, full unicode spec support and flexible image collection support. SVG sprites are not supported for performance reasons. For best results pair with https://github.com/emojione/emojione-assets.
Determines if string contains only a single emoji. Automatically trims whitespace before checking. Returns bool.
Takes a string with shortnames and returns a string with every known emoji shortname replaced with corresponding unicode representation. Ignores unknown shortnames.
Opposite of shortnamesToUnicode
.
Takes a string with shortnames and returns a string with every known emoji shortname replaced with an image tag. Useful for rendering specific emojis when it's easier to use :bacon:
instead of 🥓. For a list of supported options check below.
Takes a string with unicode emojis and returns a string with every known emoji sequence replaced with an image tag. Useful for rendering user generated content. For a list of supported options check below.
An array of objects containing all supported emojis. Format is:
{
category: "people", // emoji category according to spec
hex: "1f603", // hex representation used to reference images
shortname: ":smiley:", // shortname representation, legacy so no aliases are supported
suggest: true // should this emoji appear in suggestions
}
String containing regular expression for a single emoji character supported by this library. Usage:
const myRegex = new RegExp(emojiRegex); // do stuff
Same as emojiRegex
, but for shortnames.
Render functions and some helper functions support these options. This list contains keys and their default values.
{
size: 64, // size of emojis to use when the default CDN is used
className: null, // CSS class to use when rendering image tags
unsafe: false, // when set to true, render will NOT sanitize the string, e.g. it forces "unsafe" output
single: false, // when a string contains just a single emoji this speeds render a bit
cdn: undefined, // a CDN to use for image paths
}
By default the path to emoji images is constructed like this: /images/emojis-v${version}/${size}
. version
is the https://github.com/emojione/emojione-assets version used to generate the emojis.json file and size
is the asset size (32/64/128). Example output: /images/emojis-v4.0.0/64/1f603.png
. When cdn
option is specified, it will be used instead. When just a size
is specified, default path will be used with size
being replaced by the one provided in options.
FAQs
Converts emojis to images
The npm package emojitsu receives a total of 3 weekly downloads. As such, emojitsu popularity was classified as not popular.
We found that emojitsu demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
Security News
Biden's executive order pushes for AI-driven cybersecurity, software supply chain transparency, and stronger protections for federal and open source systems.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.