defineStore()
Declares a store. Two overloads β see Defining Stores for the difference in practice.
Store instance
Every store β however it was defined β has the same built-in members alongside its own state/getters/actions:
useStore()
The hook for functional components. Takes a store definition (what defineStore() returned) and returns the live store, subscribed so the calling component re-renders when it changes.
connectStore()
The class-component equivalent of useStore() β see Class Components for full usage. Two equivalent call shapes, depending on where the store map lives:
<NekutaStore>
Root component for a Nekuta-powered app: creates a Nekuta instance and makes it available to useStore()/connectStore() below it in the tree, via React Context β in one step.
createNekuta()
Creates a new Nekuta instance β the root object every store lives on, the equivalent of Pinia's createPinia(). Typically created once per app (client-side) or once per request (server-side β see SSR & Next.js).
storeToRefs()
Splits a store's state and getters off into individually-subscribable refs β the same purpose as Pinia's storeToRefs()
SSR helpers
Covered in depth in Hydration & skipHydrate β this page is the quick signature reference.
@nekuta/next
Covered with full examples in SSR & Next.js β this page is the quick signature reference. One package, plain named exports (no subpath split β see the project's build plan for why), internally organized by router.