---
title: "Comment by Dinys Monvoisin on \"Using React Context API with NextJS\" | Hashnode"
description: "The issue I found using React Context API is that the number of nested components increase as your props increase. People should determine at first hand how com"
url: "https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3/comment/5f9f9b4fde85d46a77d5ee8e"
---

[Discussion](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3)

Comment [Using React Context API with NextJS](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3)

[Dinys Monvoisin](https://hashnode.com/@dinmon)

[Nov 2, 2020](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3/comment/5f9f9b4fde85d46a77d5ee8e)

The issue I found using React Context API is that the number of nested components increase as your props increase.

People should determine at first hand how complex their project would be to decide using React Context API or a state management library like Redux.

[Alan Montgomery](https://hashnode.com/@alanmontgomery)

[Nov 2, 2020](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3/comment/5f9f9b4fde85d46a77d5ee8e#reply-5f9fbab5de85d46a77d5f05b)

Yeah a definite valid point.