synstate 3.0.3 → 3.0.4

package/README.md

@@ -17,7 +17,7 @@
 
 "SynState" is named after "Synchronized + State." It represents a sound synchronized state through a **glitch-free**[^1] Observable implementation.
 
-[^1]: See ["How SynState solved the glitch?"](https://noshiro-pf.github.io/synstate/internals/how-synstate-solved-the-glitch/).
+[^1]: See ["How SynState solved the glitch?"](https://noshiro-pf.github.io/mono/synstate/internals/how-synstate-solved-the-glitch/).
 
 ## Features
 
@@ -32,7 +32,7 @@
 
 ## Documentation
 
-- <https://noshiro-pf.github.io/synstate/>
+- <https://noshiro-pf.github.io/mono/synstate/>
 
 ## Installation
 
@@ -111,7 +111,7 @@ const UserProfile = (): React.JSX.Element => {
 };
 ```
 
-This is equivalent to the following code without synstate-react-hook:
+This is equivalent to the following code without synstate-react-hooks:
 
 ```tsx
 import * as React from 'react';
@@ -150,7 +150,7 @@ const UserProfile = (): React.JSX.Element => {
 };
 ```
 
-See also the [synstate-react-hooks README](../synstate-react-hooks/README.md).
+See also the [synstate-react-hooks README](https://github.com/noshiro-pf/mono/tree/main/libs/synstate-react-hooks#readme).
 
 If you're using React v17 or earlier:
 
@@ -207,7 +207,7 @@ A state management library that scales from simple global state to complex async
 
 RxJS is the most well-known Observable library, and it excels at modeling asynchronous event processing. However, RxJS has a fundamental issue known as **glitch**[^1] — a phenomenon where derived values can temporarily enter inconsistent intermediate states during synchronous propagation. For a state management library, where consistency of derived state is critical, this is unacceptable. SynState was built from scratch with a glitch-free Observable implementation to solve this problem.
 
-For a detailed explanation, see ["How SynState solved the glitch?"](https://noshiro-pf.github.io/synstate/internals/how-synstate-solved-the-glitch/).
+For a detailed explanation, see ["How SynState solved the glitch?"](https://noshiro-pf.github.io/mono/synstate/internals/how-synstate-solved-the-glitch/).
 
 ### Key Differences from RxJS
 
@@ -243,7 +243,7 @@ const [
 // type of state: InitializedObservable<number>
 // type of setState: (v: number) => number
 // type of updateState: (updater: (prev: number) => number) => number
-// type of resetState: () => void
+// type of resetState: () => number
 // type of getSnapshot: () => number
 // type of initialState: number
 

package/dist/core/types/timer.d.mts

@@ -1,12 +1,2 @@
-/**
- * Timer handle for Node.js / browser compatibility.
- *
- * Defined by what `clearTimeout` accepts rather than by what `setTimeout`
- * returns. The two are not the same type under the strict standard library:
- * `setTimeout` there returns `{} | null`, which `clearTimeout`'s
- * `number | undefined` parameter rejects. Every use of this type here is a
- * handle on its way to `clearTimeout` / `clearInterval`, so the consumer's
- * side is the one that has to fit.
- */
-export type TimerId = NonNullable<Parameters<typeof clearTimeout>[0]>;
+export type TimerId = ReturnType<typeof setTimeout>;
 //# sourceMappingURL=timer.d.mts.map

package/dist/core/types/timer.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"timer.d.mts","sourceRoot":"","sources":["../../../src/core/types/timer.mts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,MAAM,MAAM,OAAO,GAAG,WAAW,CAAC,UAAU,CAAC,OAAO,YAAY,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC"}
+{"version":3,"file":"timer.d.mts","sourceRoot":"","sources":["../../../src/core/types/timer.mts"],"names":[],"mappings":"AACA,MAAM,MAAM,OAAO,GAAG,UAAU,CAAC,OAAO,UAAU,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synstate",
-  "version": "3.0.3",
+  "version": "3.0.4",
   "description": "Type-safe State Management Library for TypeScript/JavaScript",
   "repository": {
     "type": "git",
@@ -51,8 +51,8 @@
     "prettier-plugin-packagejson": "3.0.2",
     "react": "19.2.8",
     "rxjs": "7.8.2",
-    "synstate-react-hooks": "3.0.3",
-    "synstate-react-hooks-compat": "3.0.3",
+    "synstate-react-hooks": "3.0.4",
+    "synstate-react-hooks-compat": "3.0.4",
     "ts-repo-utils": "10.6.2",
     "valtio": "2.3.2",
     "zustand": "5.0.15"

package/src/core/types/timer.mts

@@ -1,11 +1,2 @@
-/**
- * Timer handle for Node.js / browser compatibility.
- *
- * Defined by what `clearTimeout` accepts rather than by what `setTimeout`
- * returns. The two are not the same type under the strict standard library:
- * `setTimeout` there returns `{} | null`, which `clearTimeout`'s
- * `number | undefined` parameter rejects. Every use of this type here is a
- * handle on its way to `clearTimeout` / `clearInterval`, so the consumer's
- * side is the one that has to fit.
- */
-export type TimerId = NonNullable<Parameters<typeof clearTimeout>[0]>;
+// Timer types for Node.js/Browser compatibility
+export type TimerId = ReturnType<typeof setTimeout>;