DEV Community: Rubi

No Wonder why Zustand is Popular as Client-Side State Management libary

Rubi — Tue, 24 Mar 2026 05:40:07 +0000

I tested Zustand state management library in React these days. It was way less boilerplate code than Redux Toolkit, which is also a state management lib in React. If you've ever felt bogged down by the boilerplate required to get a simple global state working in Redux Toolkit (RTK), you aren't alone.

In Redux Toolkit, even a simple state change requires a fair amount of "ceremony." To get things running, you typically have to:

Create a Slice (defining initial state and reducers).
Configure the Store.
Wrap your application in a Provider to grant child components access.
Use multiple hooks (useDispatch and useSelector) just to interact with that state.

While RTK is powerful, this flow can feel like a lot of heavy lifting for smaller or medium-sized features.

In Zustand, I have to write only the store hook for state and functions ( which is like a reducer function in RTK) and directly use that hook in the component. The component directly applies state changes using that store hook, which is less complex than redux tool kits.

In conclusion, code written with Zustand is cleaner and easier to read than code written in Redux Toolkit. Since Zustand's purpose is for client-side state management, unlike the Redux toolkit, combining Zustand with TanStack Query, which is a great lib for handling server-side state managemnt would be a powerhouse combination.

Check out the code: I’ve put together a demo project comparing the two approaches here:
Cosmetic Store Demo on GitHub

Basic Git Useages

Rubi — Sun, 05 Nov 2023 16:38:41 +0000

This article is about using Git, the version control system that we are most currently using in our developer journey.

Basic Git Commands

: git init , git clone, git status, git add, git commit, git push, git fetch, git pull

git init = to create a git repository for your project.

For the first time when you create your project, and, in that project, you will use git, you need to use that command to use the other git commands for version control.

git clone = copying repository in your local

if you want to copy existing repository, git clone command is for you.

git status = checking the status of your files

If you edit or delete anything from your current stage, this command can show the status of the current stage. So, you can check which files you changed.

git add = adding modified files to your current stage

You modified or deleted some files in your current stage. To saved that changed files in your current stage, you need to use git add command.

git add . ⇒ adding all changed files to current stage.

git add ⇒ adding specific changed file to current stage

git commit = saving your changed files, which you have added in your stage

After you have added your modified files, you need to save that stage. In that time, you have to use git commit commands.

git commit -m “{message you want to show}”

git commit -a -m “{message you want others to know}”

if you use -a in git commit command, you can skip using git add command. In git commit -a -m “{Message}”, -a is adding to stage and -m is for message.

git push = to push your committed stage to remote repository from your local

If you want to push your committed files to GitHub repository, you need to use this command.

git push ⇒ push from local to remote main or master repository

git push -f ⇒ flag -f means you want to push by force.

git push -u [remote repository name] [branch name that you want to push from local] ⇒ flag -u is upstream, like tracking branch with your local branch.

PS: The best practice is you may need to git pull or git fetch before you push anything to the repository in order to reduce merge conflicts later.

git pull and git fetch ⇒ grabbing updates from your remote repository.

Between these two commands, git fetch is used for checking the latest update of your repository, but git pull merges the latest update downloaded to your local.

git fetch ⇒ fetch update from remote repository

git fetch -a ⇒ fetching updated information from all remote repositories.

git fetch ⇒ fetching specific repository.

git pull = git fetch + git merge

PS: After your git fetch, you will know which files got updated, and then you can use git diff to see the differences. You can fix and you can git merge.

You can take reference from this YouTube video for educational purposes. They explain pretty well.

(19) Git Fetch | What is Git Fetch and How to Use it | Learn Git - YouTube

How to go back directory in Nodejs?

Rubi — Mon, 06 Sep 2021 06:17:31 +0000

If you are new to Nodejs , you may not know how to use file module completely. I hope this article may help you to find out ways to create better application with Nodejs.

Nodejs is really fast than other languages' processing .All javascript lovers are now fall in love with nodejs because of its non-blocking feature and robust architecture .

Today ,I am going to show you how we can go back file directory in nodejs . Now ,we will log in console to know where we are running ,using__dirname.


console.log(__dirname);//current directory where we open this folder.

Now, we get our current directory but you are trying to move your directory one step back.You must use nodejs built in module path to work with directories. The method path.join() execute several segments into one path.


const path=require('path');
let oneStepBack=path.join(__dirname,'../');
console.log(oneStepBack);//move one step back from current directory

If you want to move two step backward from current working directory, the code will be like this...


const path=require('path');
let twoStepBack=path.join(__dirname,'../../');
console.log(twoStepBack);//move two step back from current directory

Happy coding!!