Testing
There's no createTestingPinia()-equivalent in Nekuta — no dedicated testing package at all. Stores are plain objects built on a Nekuta instance, so testing them is just... testing them, directly, with whatever test runner your app already uses (these examples use Jest).
Migrating from Pinia
If you already know Pinia, most of this is a rename exercise. The table below is the quick reference; the sections after it cover the handful of places where the mapping isn't 1:1.
Migrating from Zustand / Redux
Coming from Zustand or Redux, the biggest mental shift is that Nekuta stores aren't read with a selector function — you don't write useStore((state) => state.count). You call the store's own hook and read properties directly off what it returns:
Enforcing a Store Style
defineStore() supports two styles — see Defining Stores — and nothing about the store engine itself picks one for your project. Left alone, different stores (or different contributors) can end up mixing schema stores and hooks stores in the same codebase.