Pinia instance

The instance type returned by createPinia(), carrying the plugin list and the active flag.

Create & register

import { createPinia, setActivePinia, getActivePinia } from '@/uni_modules/ux-pinia'

// Case 1: pure state management — do nothing (the first useStore lazily creates a default instance)

// Case 2: plugins — register explicitly at the top level of main.uts
setActivePinia(
	createPinia()
		.use(pluginA)
		.use(pluginB)
)

// Read at runtime
const pinia = getActivePinia() // Pinia | null

P8 finding

On native, app.use(pinia instance) does not fire install. Mount-free (or top-level setActivePinia) is the only cross-platform-consistent form.

Pinia

Member	Signature	Notes
use	(plugin: PiniaPlugin) => Pinia	register a plugin, chainable; scheduled in registration order when a store is created
install	(app: any) => void	entry for app.use(pinia) (reliable on Web only; use setActivePinia on native)

Plugin scheduling

Each store schedules registered plugins once, at first creation (first useStore call, after setup runs):

const logger: PiniaPlugin = (ctx: PiniaPluginContext): void => {
	console.log('store created:', ctx.storeId)
	// ctx.store is any — narrow at use site: const s = ctx.store as CounterStore
}

• Plugins run exactly once per store (guaranteed by the singleton)
• Without a registered activePinia, plugins are not scheduled (mount-free mode); stores still work
• UTS constraint: plugins return void — unlike standard Pinia, they cannot return an object to merge into the store; extend behavior through the store's existing actions / state