kikobeats / emojis-list

Complete list of standard emojis.

emojis-list

Complete list of standard Unicode Hex Character Code that represent emojis.

NOTE: The lists is related with the Unicode Hex Character Code. The representation of the emoji depend of the system. Will be possible that the system don't have all the representations.

Install

npm install emojis-list --save

Usage

const emojis = require('emojis-list')
console.log(emojis[0])
// => 🀄

Related

• emojis-unicode – Complete list of standard Unicode codes that represent emojis.
• emojis-keywords – Complete list of am emoji shortcuts.
• is-emoji-keyword – Check if a word is a emoji shortcut.
• is-standard-emoji – Simply way to check if a emoji is a standard emoji.
• trim-emoji – Deletes ':' from the begin and the end of an emoji shortcut.

License

MIT © Kiko Beats

emojis-list's Issues

Uncaught TypeError: __webpack_require__(...).filter is not a function

webpack/loader-utils#36

I think there are some conflicts between webpack loader-utils emojis-list and react-router-proxy-loader

Not able to fetch package if inside private npm proxy.

We have corporate restricted nexus server to manage npm packages when tried to install within corp npm getting below error

3364 verbose stack Error: 500 javax.servlet.ServletException: org.sonatype.nexus.repository.storage.RetryDeniedException: Reached max retries: 8/8: emojis-list@^2.0.0
3364 verbose stack     at fetch.then.res (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
3364 verbose stack     at tryCatcher (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
3364 verbose stack     at Promise._settlePromiseFromHandler (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
3364 verbose stack     at Promise._settlePromise (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
3364 verbose stack     at Promise._settlePromise0 (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
3364 verbose stack     at Promise._settlePromises (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
3364 verbose stack     at Async._drainQueue (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
3364 verbose stack     at Async._drainQueues (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
3364 verbose stack     at Immediate.Async.drainQueues (/Users/anjum/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
3364 verbose stack     at runCallback (timers.js:810:20)
3364 verbose stack     at tryOnImmediate (timers.js:768:5)
3364 verbose stack     at processImmediate [as _immediateCallback] (timers.js:745:5)

I believe in package.json of emojis-list we need to add ssh something like

Current

"repository": {
    "type": "git",
    "url": "git+https://github.com/kikobeats/emojis-list.git"
  }

Expected

  "repository": {
    "type": "git",
    "url": "git+ssh://[email protected]/kikobeats/emojis-list.git"
  },

This will fix above problem

Standard heart emoji is black instead of red

https://github.com/Kikobeats/emojis-list/blob/master/index.js#L2445
I believe this should be the standard (red) heart ( https://unicode.org/emoji/charts/full-emoji-list.html#2764 ) as indicated by the keyword in https://github.com/Kikobeats/emojis-keywords/blob/master/index.js#L2445

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

map emoji names with emojis

I have emoji names like :shipit: :cat: and I want to display them as 🐱. I have looked at emojis-keywords but the array mapping is not the same meaning emoji-keywords[5] != emojis-list[5]. Do you have suggestions on how this could be achieved?

Add new emoji 12.1

Blog unicode
Unicode standard 12.1

Integrity check failed for "emojis-list"

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.