Skip to main content

Introduction

Nekuta is a React store ecosystem based on Pinia — Vue's official state management library. It aims to work the same way for the people using it: defineStore(), state, getters, actions, $patch/$subscribe/$onAction, plugins — the same shape, the same names, adapted to React instead of Vue.

Under the hood it's a from-scratch port, not a wrapper around Pinia or Vue. Nekuta ships its own small reactivity engine (a Proxy-based reactive()/ref()/computed()/effect() system modeled on @vue/reactivity) so that getters auto-memoize on the exact state they read, the same way Pinia's do — rather than the more common "manual selector" approach other React state libraries use.

Why not just use Zustand / Redux / Jotai?​

Those are all good libraries, and if you're starting fresh with no Vue background, they're worth considering too. Nekuta exists for a specific case: teams or people who already know Pinia and want the same mental model and API in a React codebase, without relearning a different store shape. If you already think in state / getters / actions, Nekuta should feel immediately familiar. See Migrating from Zustand/Redux and Migrating from Pinia if either applies to you.

Packages​

  • @devtools/core — the store engine itself: defineStore, useStore, connectStore, plugins, SSR helpers. Framework-router-agnostic.
  • @devtools/next — the Next.js adapter: SSR/hydration support for both the Pages Router and the App Router.

What's supported today​

  • Both functional components (useStore(), a hook) and class components (connectStore(), patches your class in place — no wrapper component) — React 19.
  • Schema stores (state/getters/actions, like Pinia's Options API) and hooks stores (a function returning refs/computed/functions, like Pinia's <script setup> style) — the same two flavors, converging on one engine.
  • $patch, $subscribe, $onAction, $reset, $dispose, storeToRefs(), plugins.
  • SSR/hydration for Next.js, both routers.
  • Fine-grained re-renders — a component only re-renders for the specific (deeply-nested, too) properties it actually reads, matching Pinia's DX exactly. See Reactivity Model for how.

What's intentionally not built yet​

A DevTools browser extension. Vue DevTools' Pinia integration doesn't have a React equivalent yet — planned as a separate project.

  • A dedicated testing package. There's no createTestingPinia()-equivalent; see Testing for how to test stores directly with Jest instead.

Start with Installation or jump straight to the Quick Start.