Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Feed/

Discussion

How to use Zustand's persist middleware in Next.js

Solving the hydration error occurring with Zustand's persist middleware in Next.js

Mar 13, 2023·3 min read·blog.abdulsamad.devUpdated Mar 30, 2023Read the article

#javascript
#typescript

#nextjs

#state-management

#error

Written by

Abdul Samad Ansari

@abdulsamad-ansari · Mumbai, India

View profile

I love crafting engaging web experiences and building reliable software

Web Developer and lifelong learner currently focused on Full stack MERN development. Skilled in HTML, CSS, JavaScript (ES5 and Up), React, TypeScript, Node, and MongoDB. Looking to expand my horizons in Web Development and Technology.

Responses1

Markdown supported · ⌘↵ to post

Simo D.

Oct 14, 2023

I tried this method but it caused my page to fall in a infinite loop due to the useEffect hook re-rendering the page every time the result variable changes and that same variable in used to set the state. any solution to this problem?

Abdul Samad Ansari

Oct 22, 2023

Hi Simo, The hook initially gives null and after that, the state is updated. I'm not sure why you're facing this problem. Please check the useEffect dependencies.