@playstack/search-minisearch
Fuzzy and prefix matching through MiniSearch without exposing provider types in Playstack search contracts.
Free. MIT licensed. Check preview availability before installing. See package access.
@playstack/search-minisearch implements the same mapped search contract with fuzzy matching, prefix matching, suggestions, weighted fields, synonyms, arbitrary filters, and stable result ordering.
const search = createMiniSearchEngine(records, {
document: mapSearchDocument,
fields: { title: 10, tags: 6, body: 1 },
fuzzy: { distance: 0.2, minTermLength: 4 },
prefix: { enabled: true, lastTermOnly: true, minTermLength: 2 },
})Only values placed in the mapped result can leave the index. The adapter snapshots input at construction and runs in both Node and Workers runtimes.
Install
After confirming preview access, install the package at your application's shared Playstack version:
npm install --save-exact @playstack/search-minisearch@0.1.0-beta.1Check the peer requirements below before choosing a runtime or provider.
API entry points and requirements
Reference snapshot: @playstack/search-minisearch@0.1.0-beta.1. Import only the entry point your runtime needs. Paths below are relative to the installed package; use Go to Definition in your editor to inspect exact parameters, return types and overloads. Do not import the declaration-file paths directly.
| Public entry point | Declaration file |
|---|---|
@playstack/search-minisearch | ./dist/index.d.ts |
@playstack/search-minisearch/package.json | No TypeScript declaration (asset or metadata export). |
Node.js engine requirement: >=20. This is not a claim that every entry point works in browsers or Workers.
Peer dependencies
Keep existing framework versions that satisfy these ranges. Install optional peers only when using the corresponding adapter. The package manager resolves ordinary dependencies separately.
| Peer | Compatible range | When needed |
|---|---|---|
@playstack/search | 0.1.0-beta.1 | Required by the package. |
For a complete first program, start with Getting started. For API lookup and partial-example conventions, see Reading the reference. Provider failures, lifecycle requirements and application responsibilities remain described in the guide above; types alone do not establish production safety.