I'm not sure if this is the best fix, but doing the require dynamically fixes the bug. Perhaps this is next related as well. (also hi matt it's been a long time : ) 👋 )
hrm, the only thing i can think of is that next.js changed the way they resolve things. anyway the change is in next-cookies@1.0.2. thanks for the fix!
The current code was causing issues in the browser with next@3.0.1-beta.19. Was getting an error on client side page changes:
I'm not sure if this is the best fix, but doing the require dynamically fixes the bug. Perhaps this is next related as well. (also hi matt it's been a long time : ) 👋 )