Search and local-first foundations

Two new capability families grew out of integrations that needed reusable mechanics without surrendering their product vocabulary.

@playstack/search provides weighted lexical indexing, stable ranking, synonyms, filters, grouping, a Fetch boundary, and a validated HTTP client. Products map their own records and result shapes into the contract. Chakra Docs can retain its document model while sharing the engine and transport primitives.

MiniSearch is available as an optional provider. Next.js bindings cover both App and Pages Router handlers, while the NestJS package exposes the same protocol through an application-configured service and controller.

Shared local-first contracts

@playstack/local-first owns atomic local mutations, a durable outbox, cursor pulls, idempotent change application, retry and dead-letter outcomes, conflict hooks, upcasting, and runtime leases. It deliberately leaves product entities, authentication, attachments, and server change sources outside the core.

IndexedDB and Expo SQLite packages implement real platform storage and runtime coordination behind the same conformance contract. React, Tauri SQLite, and a Nest server binding remain planned until additional reference consumers stabilize those boundaries.

Go

Playstack Pro tag
OriginsPricingBlogNewsletterChangelogStatusRoadmap
ContributorsCommunityIn Use ShowcaseCase StudiesPartnersSponsors
FAQsSupportContact

© 2026 Playstack. All rights reserved.

With OSS
Terms of ServicePrivacy PolicyCookie PolicyImprint

By

Commune Software