Package Exports
- swr-global-state
- swr-global-state/dist/index.js
- swr-global-state/dist/swr-global-state.esm.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (swr-global-state) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
♻️ SWR Global State
Zero-setup & simple global state management for React Components based on SWR helpers. With this library, you can focus on your awesome React Project and not waste another afternoon on the setup & configuring your global state. 🌄
Table of Contents
- ♻️ SWR Global State
- Table of Contents
- Getting Started
- Demo
- FAQ
- Publishing
- License
- Feedbacks and Issues
- Support
Getting Started
Install
npm install swr-global-state
or
yarn add swr-global-state
Usage
Create a store object
Create a new file for your global state on your root directory. Example: stores/app.js
// file: stores/app.js
export const APP_COUNT = {
key: "@app/count", // (Required) state key
initial: 0, // <- (Required) initial state
persist: false // <- (Optional) if you want to persist the state to local storage, then set it to true.
};
Using store on your component
// file: components/SetCountComponent.js
import { useStore } from "swr-global-state";
import { APP_COUNT } from "stores/app";
function SetCountComponent() {
const [count, setCount] = useStore(APP_COUNT);
return (
<div>
<button onClick={() => setCount(count - 1)}>
(-) Decrease Count
</button>
<button onClick={() => setCount(count + 1)}>
(+) Increase Count
</button>
</div>
);
}
export default SetCountComponent;
// file: components/GetCountComponent.js
import { useStore } from "swr-global-state";
import { APP_COUNT } from "stores/app";
function GetCountComponent() {
const [count] = useStore(APP_COUNT);
return (
<div>
<p>Current Count: {count}</p>
</div>
);
}
export default GetCountComponent;
TypeScript
// file: stores/app.ts
import type { StoreParams } from "swr-global-state";
export const APP_COUNT: StoreParams<number> = {
key: "@app/count",
initial: 0,
persist: false
};
// interface Store is generic type. It must be passed type parameter
Best Practice
Custom hooks
Instead of creating store object in stores/app.js
file, you can create a custom hooks with createStore()
. Example: stores/count.js
.
// file: stores/count.js
import { createStore } from "swr-global-state";
const useCount = createStore({
key: "@app/count", // (Required) state key
initial: 0, // <- (Required) initial state
persist: true // <- (Optional) if you want to persist the state to local storage, then set it to true.
});
export default useCount;
Using store on your component
// file: components/SetCountComponent.js
import useCount from "stores/count";
function SetCountComponent() {
const [, setCount] = useCount(); // <- `[, ]` skipping first index of the array.
return (
<div>
<button onClick={() => setCount(prev => prev - 1)}>
(-) Decrease Count
</button>
<button onClick={() => setCount(prev => prev + 1)}>
(+) Increase Count
</button>
</div>
);
}
export default SetCountComponent;
// file: components/GetCountComponent.js
import useCount from "stores/count";
function GetCountComponent() {
const [count] = useCount();
return (
<div>
<p>Current Count: {count}</p>
</div>
);
}
export default GetCountComponent;
Example custom hooks with TypeScript
// file: stores/count.ts
import { createStore, StoreHooks } from "swr-global-state";
const useCount: StoreHooks<number> = createStore({
key: "@app/count",
initial: 0
});
export default useCount;
or you still can wrap useStore
in another function with yourself
// file: stores/count.ts
import useStore, { Store } from "swr-global-state";
function useCount(): Store<number> {
return useStore<number>({
key: "@app/count",
initial: 0
});
}
export default useCount;
Demo
You can see:
FAQ
Why should I use this?
- If you want to manage your global state like
useState
as usual. - If you want to manage your global state without involving in setting up Provider Component, Dispatcher, Reducer, etc.
- If you want to see
Redux
orContext API
alternative. - If you're already use
SWR
, but you have no idea how to manage synchronous global state withSWR
on client-side. - If you're still use
Redux
orContext API
, but you are overwhelmed with their flow.
If this library can cover Redux
, how about asynchronous state management like redux-saga
, redux-thunk
, or redux-promise
?
At this point, swr-global-state
only handles synchronous global state in client-side. If you want to handle the asynchronous global state requested from the API, maybe you should use a library like SWR or TanStack Query . But I recommend SWR
, because this swr-global-state
is built and depends on SWR
helpers, and you don't need to install other libraries.
So the conclusion is, if you use SWR + swr-global-state, you basically don't need to use Redux
or Context API
anymore.
Publishing
- Before pushing your changes to Github, make sure that
version
inpackage.json
is changed to newest version. Then runnpm install
for synchronize it topackage-lock.json
- After your changes have been merged on branch
main
, you can publish the packages by creating new Relase here: https://github.com/gadingnst/swr-global-state/releases/new - Create new
tag
, make sure thetag
name is same as theversion
inpackage.json
. - You can write Release title and notes here. Or you can use auto-generated release title and notes.
- Click
Publish Release
button, then wait the package to be published.
License
swr-global-state
is freely distributable under the terms of the MIT license.
Feedbacks and Issues
Feel free to open issues if you found any feedback or issues on swr-global-state
. And feel free if you want to contribute too! 😄
Support
Global
Indonesia
Built with ❤️ by Sutan Gading Fadhillah Nasution on 2022