DocsBrowse documentation

@slithy/frimousse

@slithy/frimousse is a compatibility-conscious fork of the open-source Frimousse emoji picker, extending the base picker with additive seams for mixed-item workflows, richer search, consumer-owned frequent items, and companion metadata tooling.

Fork overview

Frimousse is a strong base picker. This fork exists to keep that lightweight, composable core while filling in the extension seams that production apps often need.

In practice, that mainly means mixed native and custom emoji sections, richer search behavior, consumer-owned frequent items, and clearer paths for self-hosted emoji data and fallback rendering.

The result is still a headless picker, not a batteries-included widget. The rest of the docs explain what the fork adds directly, what remains consumer-owned, and which optional companion packages handle broader emoji metadata policy.

At a glance

Topic@slithy/frimousse
Picker styleHeadless, composable React picker
Native emoji dataRuntime fetch by default, self-hostable with emojibaseUrl
Offline supportYes, when you stage and self-host the needed Emojibase files
Custom emojiYes, via supplemental and custom emoji helpers
Frequent or recent itemsConsumer-owned persistence, helper-supported ranking and section building
Native search enrichmentVia @slithy/emoji-transforms
Fallback image policyVia @slithy/emoji-compat
Best fitApps that want control over styling, data delivery, and emoji policy

Package boundaries

@slithy/frimousse

Owns the picker UI, picker behavior, additive picker extension seams, and selection/search/render behavior that is intrinsic to the picker.

@slithy/emoji-transforms

Owns metadata transforms such as native search terms, labels, shortcodes, and locale-aware metadata maps. Use it to prebuild app-owned data artifacts from Emojibase-style datasets instead of pushing that policy into the picker runtime.

@slithy/emoji-compat

Owns native support detection and fallback-image metadata. It does not render emoji or choose your app’s fallback policy.

Where next