@octanejs/jotai 0.1.32 → 0.1.34

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/jotai",
-  "version": "0.1.32",
+  "version": "0.1.34",
   "license": "MIT",
   "type": "module",
   "engines": {
@@ -46,7 +46,7 @@
     "jotai": "^2.20.2"
   },
   "peerDependencies": {
-    "octane": "0.1.35"
+    "octane": "0.1.37"
   },
   "devDependencies": {
     "@tsrx/react": "^0.2.56",
@@ -54,7 +54,7 @@
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
     "vitest": "^4.1.10",
-    "octane": "0.1.35"
+    "octane": "0.1.37"
   },
   "scripts": {
     "test": "vitest run"

package/src/react/Provider.tsrx

@@ -3,17 +3,17 @@
 // otherwise); the port keeps that laziness but renders through a SINGLE JSX
 // path instead of upstream's two createElement returns — the children
 // descriptor shape must stay stable across renders for octane's reconciler.
-import { useRef } from 'octane';
+import { useRef, type OctaneNode } from 'octane';
 import { createStore } from 'jotai/vanilla';
-import { StoreContext } from './store.ts';
+import { StoreContext, type Store } from './store.ts';
 
-export function Provider(props) @{
+export function Provider(props: { children?: OctaneNode; store?: Store }) @{
 	const { children, store } = props;
 
-	const storeRef = useRef(null);
+	const storeRef = useRef<Store | null>(null);
 	if (!store && storeRef.current === null) {
 		storeRef.current = createStore();
 	}
 
-	<StoreContext.Provider value={store || storeRef.current}>{children}</StoreContext.Provider>
+	<StoreContext.Provider value={store || storeRef.current!}>{children}</StoreContext.Provider>
 }

package/src/react/useAtomValue.ts

@@ -20,6 +20,12 @@ import type { Atom, ExtractAtomValue } from 'jotai/vanilla';
 import { useStore, type Store } from './store';
 import { splitSlot, subSlot } from '../internal';
 
+// The consumer's bundler substitutes the whole `process.env.NODE_ENV` expression
+// below, so it must stay written out literally. Declared module-locally — never
+// `declare global`, which would ship in the tarball — so this file type-checks in
+// a browser app that has no `@types/node`.
+declare const process: { env: { NODE_ENV?: string } };
+
 const isPromiseLike = (x: unknown): x is PromiseLike<unknown> =>
 	typeof (x as PromiseLike<unknown>)?.then === 'function';
 

package/src/react/useSetAtom.ts

@@ -6,6 +6,12 @@ import type { ExtractAtomArgs, ExtractAtomResult, WritableAtom } from 'jotai/van
 import { useStore, type Store } from './store';
 import { splitSlot, subSlot } from '../internal';
 
+// The consumer's bundler substitutes the whole `process.env.NODE_ENV` expression
+// below, so it must stay written out literally. Declared module-locally — never
+// `declare global`, which would ship in the tarball — so this file type-checks in
+// a browser app that has no `@types/node`.
+declare const process: { env: { NODE_ENV?: string } };
+
 type SetAtom<Args extends unknown[], Result> = (...args: Args) => Result;
 type Options = Parameters<typeof useStore>[0];
 

package/src/react/utils.ts

@@ -11,6 +11,12 @@ import { useSetAtom } from './useSetAtom';
 import { useAtom } from './useAtom';
 import { splitSlot, subSlot } from '../internal';
 
+// The consumer's bundler substitutes the whole `process.env.NODE_ENV` expression
+// below, so it must stay written out literally. Declared module-locally — never
+// `declare global`, which would ship in the tarball — so this file type-checks in
+// a browser app that has no `@types/node`.
+declare const process: { env: { NODE_ENV?: string } };
+
 type SetAtomOptions = Parameters<typeof useSetAtom>[1];
 
 // useResetAtom — port of react/utils/useResetAtom.ts.