night roost
My component previously sent a prop "hoverColor" (optional prop) to an Icon component, but even after I removed it (not passing the prop anymore), the component still logs the hoverColor with its previous/old value.
I1ve tried to restart the dev server, still there.
marsh crestBOT
Hi @night roost. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
It seems like you are experiencing an issue with stale props data in Next.js 14.2. This could be related to caching behavior in Next.js. Here are a few steps you can take to troubleshoot and resolve this issue:
Clear the .next Folder: Sometimes, stale data can persist due to caching in the .next folder. Try deleting the contents of the .next folder and restarting the development server. This can be done with the following commands:
rm -rf .next
next dev
Disable Browser Cache: Ensure that your browser cache is disabled while you are developing. This can be done in the browser's developer tools under the Network tab by checking the "Disable cache" option.
Check for Static Props: If you are using getStaticProps, remember that in development mode (next dev), getStaticProps will be called on every request. This should ensure that you are getting the latest data. Refer to the Next.js documentation (https://nextjs.org/docs/pages/building-your-application/data-fetching/get-static-props#runs-on-every-request-in-development) for more details.
In development (`next dev`), `getStaticProps` will be called on every request.
Inspect Component State: Ensure that your component is not holding onto the old state or props internally. Sometimes, React components can retain state if not properly updated.
If the issue persists, you might want to check if there are any related issues on the Next.js GitHub repository. For example, there was a similar issue reported where cached data was displayed when navigating back to a page (GitHub Issue #59958 (https://github.com/vercel/next.js/issues/59958)).