Fuse VS fuzzyset.js

oh very cool. would love to see the comparison/benchmark against the library I've used in projects for years (Fuse - https://github.com/krisk/Fuse).

Keep up the great work!

It has the merit of being accomplished. Good work ! You can use https://fusejs.io/ to improve your search feature ;)

I had a very similar task and solved it with https://fusejs.io/ and was very happy with the result. Great performance and was able to get the exact config I wanted very easily.

You can use this https://fusejs.io/ library to implement a fuzzy search but you’ll have to put all the content you want to be searchable in a json along with the url it’s in so when you click on a result, you can redirect the user to the page you want.

Check the docs for your component system's text input component. Not all have specific autocomplete Search components like MUI, you might have to make your own out of your library's text input and menu components plus a fuzzy search library like Fuse.js.

I'm looking for a fuzzy search JavaScript library to filter an array. I've tried using fuzzyset.js and fuse.js, but the results are terrible (there are demos you can try on the linked pages).

> 2. How much can one reasonably expect to earn per user per month or year in your experience? (My extension is by no means mission critical but it solves a (simple) problem rather elegantly IMHO).

There's no way to tell for sure! It really depends on the value the extension provides, your market, exposure and reviews on the Chrome store, etc.

I can say that one of the extensions that uses ExtensionPay is a really simple utility that allows switching between recently used tabs in Chrome (https://chrome.google.com/webstore/detail/alt-%20-q-switch-r...) but users love it and it makes a surprising amount of money!

But all that is ultimately speculative for your extension. One reason I made ExtensionPay was to lower the barrier to making paid extensions enough so instead of speculating you could just try it out and see what happens!

> 1. Is there a socially acceptable path to go from free to non-free?

From what I've seen there will be a very loud but very small minority of users that will get angry and leave bad reviews. I think if you try to make these users happy (maybe by giving them free access?) and let the others know why you're asking them to pay then it will go alright. Here's what I wrote about charging for a previously-free JavaScript library: https://github.com/Glench/fuzzyset.js#license