Do fuzzy matching using FZF algorithm in JavaScript
moduleResolution
is set to nodenext
, node16
or bundler
(https://github.com/ajitid/fzf-for-js/pull/119 by @kidonng)Want to migrate? We have prepared a guide to help you migrate from v0.4.
options.tiebreakers
has been modified, and it now matches with original FZF (https://github.com/ajitid/fzf-for-js/pull/75 by @reinhrst)⚠️ We have removed this release from NPM.
Please use v0.5.1 or above instead. Because of a bug, this version required at least Node.js 16 and NPM 8 to work.
Want to migrate? We have prepared a guide to help you migrate from v0.3.
"v2"
(default) gives you better highlighting for matched characters while "v1"
compensates that for speed.forward
.options.cache
is removed. As a result, no caching is performed.options.maxResultItems
has now been renamed to options.limit
normalize
is now on by default. This means we'll automatically remove diacritics/accents from Caffè to make it Caffe for example. This can be toggled off in options
.forward
is now on by default. This means earlier querying "abc" on "xabc yabc" used to highlight last occurrence (abc of yabc). Now first occurence (abc of xabc) will be highlighted instead. This can be toggled off in options
.positions
is now a Set. Earlier it could either be an array or a null.entry.result.score
will now be written as entry.score
. Same applies for start
and end
.This is the very first public preview release. Being a 0.x means that breaking changes could be introduced by incrementing its minor version.
find
helps you to fuzzy find on a list. If you are familiar with FZF CLI options, this does a non-extended match using V2 algorithm.