Update to emoji-regex v9
See original GitHub issue@Favna wrote a very informative explanation about emoji-regex status and its integration with the emoji image libraries we are using here.
We have now to agree on the direction we want the library to take with that regard. The options I could infer from his writing are:
- Don’t update to Unicode 13.
- Update to Unicode 13 but keep EmojiOne on v2 (no Unicode 13 support).
- Update to Unicode 13 and place a notice about usage of EmojiOne for commercial usage.
- Update to Unicode 13 and drop EmojiOne.
Please tell me if I’m forgetting anything or you can think of another solution not mentioned above. Looking forward to your opinions.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Emoji-regex NPM - npm.io
Update emoji -test-regex-pattern as described in its repository. Bump the emoji-test-regex-pattern dependency to the latest version. Update the Unicode data ...
Read more >Updating Buildkite for Emoji 4.0
Once again, the time has come to update some of the most critical of Buildkite's infrastructure — our emoji support! ✨.
Read more >Actions · mathiasbynens/emoji-regex - GitHub
A regular expression to match all Emoji-only symbols as per the Unicode Standard. - Actions · mathiasbynens/emoji-regex.
Read more >emoji-regex - npm
A regular expression to match all Emoji-only symbols as per the Unicode Standard.. Latest version: 10.2.1, last published: 3 months ago.
Read more >remove unicode emoji using re in python - Stack Overflow
Of course, the regex is already out of date, as it doesn't cover Emoji defined in newer Unicode releases; it appears to cover...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It sounds like this update necessitates a breaking update as either Emojione is removed or it becomes JoyPixel. I do think there is value in keeping JoyPixel for OSS users and I don’t blame them for having a commercial license. There is a relatively clean way to achieve this:
commercialLicenseAcknowledged– if it isn’t set to true then the JoyPixel render component throws an error.Thoughts?
Hey @Geczy , I only see dependencies bumps and formatting changes on your fork, but please feel free to work in this issue if you like 😁 (and even better, open a PR so others can benefit from it !)