use(props.params) vs useParams() in Client Component in Next.js
What is better and more ideal in Next.js 15? Does using a different one make any difference?
On Server Components the await props.params seems to be the way to go but on Client Components...
I kinda tend on using useParams() to save a render but I'm not so sure about that.
Any advice here? Im sure both work fine but I'm just curious in what works better.
On Server Components the await props.params seems to be the way to go but on Client Components...
I kinda tend on using useParams() to save a render but I'm not so sure about that.
Any advice here? Im sure both work fine but I'm just curious in what works better.
Solution
Unless you dig into the implementation details of “useParams()” you’ll see if it saves a render or not, maybe it’s implementing the same logic under the hood and they literally work the same, but who knows.
Also, a rerender isn’t much of a problem, it’ll just commit once which is the heavy duty for the browser most of the time, re-render doesn’t mean “re-create the DOM elements” it means “just read the component logic again and decide whether or not to commit again”, and it might not commit again since it’s the same tree… unless it’s not the same tree due to the implementation details of the “useParams()” hook
Also, a rerender isn’t much of a problem, it’ll just commit once which is the heavy duty for the browser most of the time, re-render doesn’t mean “re-create the DOM elements” it means “just read the component logic again and decide whether or not to commit again”, and it might not commit again since it’s the same tree… unless it’s not the same tree due to the implementation details of the “useParams()” hook
