flexsearch
nanoid
Our great sponsors
flexsearch | nanoid | |
---|---|---|
12 | 82 | |
11,765 | 23,140 | |
3.6% | - | |
7.1 | 8.3 | |
3 months ago | 11 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flexsearch
-
Nextra 2 – Next.js Static Site Generator
Full-text search is powered by FlexSearch and Nextra will index all of your pages at build time ⚡.
-
How to link search results back to original HTML when clicked?
I have a web page that reads in various .md files and displays them as HTML. The app uses the marked library to convert the markdown into HTML for display. I create a flexsearch search index out of the raw text values from the documents (raw text is gathered using DOMParser over all HTML elements) so that user can search for keywords in the docs and get back a table of results. The order of operations and search index code looks like:
-
How can I set up this Typescript project to use a Javascript library?
I am trying to get flexsearch (a lib written in js) up and running in a TS project and found a working example here. I downloaded the project and ran 'yarn add flexsearch' and also 'yarn add @/types/flexsearch' since I know that you need a special index.d.ts file to convert the JS to TS properly.... however the code errors out during the Index object creation with the message.
-
Best way to implement a search feature over raw HTML using Typescript/React?
Try using a proper browser search like Lunr or Flexsearch
-
Lyra: Fast, in-memory, typo-tolerant, full-text search engine in TypeScript
Current version of FlexSearch (0.7.2) is not typo tolerant, see https://github.com/nextapps-de/flexsearch/issues/118
-
Writing a Fuzzy Search Component With Preact and Fuse for Astro
Very nice! Seems to perform very well. I'm curious, have you compared Fuse with other search engines? Like flex search or elasticlunr? Why did you choose fuse ?
-
Comparing English and Spanish Words in JavaScript
I actually looked into this term before localeCompare(): Full Text Search. It's pretty heavy duty. In JavaScript, this can come in the form of a library dependency like FlexSearch. Far too bulky for the humble sorting task I have at hand.
- Quick live-search on 1M strings in React native
-
In memory full text search in Rust?
Javascript seems to have a comprehensive in memory solution https://github.com/nextapps-de/flexsearch
-
DynamoDB full text search
Another option that was often suggested to me was building the search index with a library such as https://github.com/nextapps-de/flexsearch and distribute the index than to the client and handle it one the client. But yeah sounds like a lot of overhead and I haven't tried it.
nanoid
- Nano ID Collision Calculator
-
Why we chose Bun
Our API is in node. And God, how I suffered to import nanoid in an esmodule project. I had to vendor it, since using a previous version was not ideal. With bun, we can no longer worry about that. Just import what you need and done.
-
UUIDv7 is coming in PostgreSQL 17
No thread about UUID is complete without a plug for NanoID! https://github.com/ai/nanoid/blob/main/README.md
-
Building a File Storage With Next.js, PostgreSQL, and Minio S3
Generate a unique file name using the nanoid library.
-
Building a Multi-Tenant App with FastAPI, SQLModel, and PropelAuth
The syntax should read similar to SQL itself. We’re using a Python port of nanoid to generate our IDs. There’s only one thing missing… how do we actually create the table?
-
You Don't Need UUID
I usually go for Nano Id for new projects https://github.com/ai/nanoid
-
Enhance Your Web Apps: Best JS Libraries 🔧
Nano ID
-
Analyzing New Unique Identifier Formats (UUIDv6, UUIDv7, and UUIDv8) (2022)
In another comment I mentioned I use nanoid in my projects now. It has a default space of 64^21 and has an a page where you can play with key lengths and alphabet sizes and see the probability of collisions :
https://zelark.github.io/nano-id-cc/
At the default 64 character alphabet with a 21 character key length it would take ~41 million years in order to have a 1% probability of at least one collision if you generated 1000 ids per second.
-
How I use Nano ID in Rails
Using randomly generated IDs like Nano ID could be a good alternative, however, as a developer, we must understand what Nano ID really does in our application. Defining the number of characters in the generated IDs is also important, to help with that Nano ID has a Collision Calculator to give us how many years in order to have a 1% probability of collision.
-
How debugging for accessibility helped me finally understand useRef
IDs used here for buttons and tasks must be unique to work correctly. This is ensured by using the nanoid package, which automatically generates unique ids.
What are some alternatives?
minisearch - Tiny and powerful JavaScript full-text search engine for browser and Node
snowflake - Snowflake is a network service for generating unique ID numbers at high scale with some simple guarantees.
Fuse - Lightweight fuzzy-search, in JavaScript
ksuid - K-Sortable Globally Unique IDs
elasticsearch-js - Official Elasticsearch client library for Node.js
typedorm - Strongly typed ORM for DynamoDB - Built with the single-table-design pattern in mind.
itemsjs - Extremely fast faceted search engine in JavaScript - lightweight, flexible, and simple to use
pg_random_id - Provides pseudo-random IDs in Postgresql databases
TNTSearch - A fully featured full text search engine written in PHP
jest - Delightful JavaScript Testing.
lunr.js - A bit like Solr, but much smaller and not as bright
Numeral-js - A javascript library for formatting and manipulating numbers.