TypeError: (0 , next__WEBPACK_IMPORTED_MODULE_4__.usePathname) is not a function
Answered
huda hajira posted this in #help-forum
help me to solve this issue, my use client is persent, everything seems fine stll
Answered by huda hajira
Disclaimer: I'm still new to Next.js so I'm very sorry for the messy syntax. I wrote this off the top of my head.
After a number of restarts and tests with both browsers, I was not able to reproduce the runtime error. However, when I added a third component (essential a duplicate of my test component) the same Unhandled Runtime Error returned (in just Safari). In this case, clearing the cache cleared the error (independent caches so not surprising.)
I would not call this a "solution" , but I am hoping that some of this information might trigger some insight by someone more talented. At a minimum it is a possible work around
After a number of restarts and tests with both browsers, I was not able to reproduce the runtime error. However, when I added a third component (essential a duplicate of my test component) the same Unhandled Runtime Error returned (in just Safari). In this case, clearing the cache cleared the error (independent caches so not surprising.)
I would not call this a "solution" , but I am hoping that some of this information might trigger some insight by someone more talented. At a minimum it is a possible work around
1 Reply
Disclaimer: I'm still new to Next.js so I'm very sorry for the messy syntax. I wrote this off the top of my head.
After a number of restarts and tests with both browsers, I was not able to reproduce the runtime error. However, when I added a third component (essential a duplicate of my test component) the same Unhandled Runtime Error returned (in just Safari). In this case, clearing the cache cleared the error (independent caches so not surprising.)
I would not call this a "solution" , but I am hoping that some of this information might trigger some insight by someone more talented. At a minimum it is a possible work around
After a number of restarts and tests with both browsers, I was not able to reproduce the runtime error. However, when I added a third component (essential a duplicate of my test component) the same Unhandled Runtime Error returned (in just Safari). In this case, clearing the cache cleared the error (independent caches so not surprising.)
I would not call this a "solution" , but I am hoping that some of this information might trigger some insight by someone more talented. At a minimum it is a possible work around
Answer