@playstack/local-first-expo
Expo SQLite persistence and injected mobile lifecycle coordination for Playstack Local First.
Pro. Covered by the Playstack Pro License. Registry access is required; check preview availability before installing. See package access.
@playstack/local-first-expo accepts an open Expo SQLite database and uses exclusive transactions so product state and synchronization records commit or roll back together.
const storage = createExpoSqliteLocalFirstStorage({ database })
const runtime = createExpoLocalFirstRuntime({
client: { netInfo, appState },
isOnline: () => netInfo.isConnected ?? true,
isForeground: () => appState.currentState === 'active',
subscribe: subscribeToMobileWakeEvents,
})The application owns the database file, product schema, NetInfo and AppState dependencies, and background-execution policy. The runtime lease is process-local, so server idempotency remains required.
Install
After confirming preview access, install the package at your application's shared Playstack version:
npm install --save-exact @playstack/local-first-expo@0.1.0-beta.1Check the peer requirements below before choosing a runtime or provider.
API entry points and requirements
Reference snapshot: @playstack/local-first-expo@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/local-first-expo | ./dist/index.d.ts |
@playstack/local-first-expo/package.json | No TypeScript declaration (asset or metadata export). |
@playstack/local-first-expo/playstack.integration.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
This package declares no peer dependencies. Its ordinary dependencies are resolved by the package manager.
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.