CodeVetter · Repo Unpack · System map
pmndrs/jotai
The repository separates the vanilla dependency engine from its React adapter and utility modules. The published artifact is an ESM library, while the website and examples are separate applications with their own dependencies. Storage is in memory unless a utility connects an atom to an external adapter. Build and release behavior is defined by package scripts and GitHub Actions.
- src/index.ts re-exports the vanilla and React APIs; separate barrels expose atom/store primitives and Provider/hooks, including the v3 raw-value hooks.
- package.json defines seven library entrypoints, publishes only dist, declares sideEffects:false, and provides TypeScript declarations only for >=5.5; React >=18 is an optional peer.
- atom() creates configuration objects with read/write functions and optional init values; createStore() delegates to INTERNAL_buildStoreRev4 unless overridden.
- buildStore owns per-store weak maps for atom state, mounting, and invalidation, sets for changes and lifecycle callbacks, and a store epoch holder; its public surface is get/set/sub.
- Provider supplies either an explicit store or a lazily created store retained in useRef; useStore selects options.store, then context, then the module's default store.
- The root build emits src into dist through tsc --noCheck; type checking is a separate test:types script. Compilation uses strict NodeNext modules and an ES2020 target.
- The Gatsby website sources ../docs as MDX, indexes documents through Algolia, and has Vercel function configuration for api/*.js; the Hacker News example independently uses Vite and React.
- Publishing runs on published GitHub releases and builds before pnpm publish; preview releases build and invoke pkg-pr-new with example templates. The pnpm workspace contains the root and website.