feat: upgrade tanstack store versions with useSelector hook (#202)

* feat: upgrade tanstack store versions with useSelector hook

* changeset

Author: KevinVandy

.changeset/lucky-buckets-beam.md

@@ -0,0 +1,11 @@
+---
+'@tanstack/react-pacer-devtools': minor
+'@tanstack/pacer-devtools': minor
+'@tanstack/angular-pacer': minor
+'@tanstack/preact-pacer': minor
+'@tanstack/react-pacer': minor
+'@tanstack/solid-pacer': minor
+'@tanstack/pacer': minor
+---
+
+feat: upgrade to tanstack store with useSelector hook

docs/framework/preact/reference/interfaces/PreactAsyncBatcher.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/async-batcher/useAsyncBatcher.ts:55](https://githu
 #### Deprecated
 
 Use `batcher.state` instead of `batcher.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactAsyncDebouncer.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/async-debouncer/useAsyncDebouncer.ts:56](https://g
 #### Deprecated
 
 Use `debouncer.state` instead of `debouncer.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactAsyncQueuer.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/async-queuer/useAsyncQueuer.ts:55](https://github.
 #### Deprecated
 
 Use `queuer.state` instead of `queuer.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactAsyncRateLimiter.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/async-rate-limiter/useAsyncRateLimiter.ts:56](http
 #### Deprecated
 
 Use `rateLimiter.state` instead of `rateLimiter.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactAsyncThrottler.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/async-throttler/useAsyncThrottler.ts:56](https://g
 #### Deprecated
 
 Use `throttler.state` instead of `throttler.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactBatcher.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/batcher/useBatcher.ts:52](https://github.com/TanSt
 #### Deprecated
 
 Use `batcher.state` instead of `batcher.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactDebouncer.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/debouncer/useDebouncer.ts:56](https://github.com/T
 #### Deprecated
 
 Use `debouncer.state` instead of `debouncer.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactQueuer.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/queuer/useQueuer.ts:52](https://github.com/TanStac
 #### Deprecated
 
 Use `queuer.state` instead of `queuer.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***
 

docs/framework/preact/reference/interfaces/PreactRateLimiter.md

@@ -49,8 +49,8 @@ Defined in: [preact-pacer/src/rate-limiter/useRateLimiter.ts:56](https://github.
 #### Deprecated
 
 Use `rateLimiter.state` instead of `rateLimiter.store.state` if you want to read reactive state.
-The state on the store object is not reactive, as it has not been wrapped in a `useStore` hook internally.
-Although, you can make the state reactive by using the `useStore` in your own usage.
+The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
+Although, you can make the state reactive by using the `useSelector` in your own usage.
 
 ***