Next.js client-side error on production in the version 4.3.0 · Issue #81 · andreizanik/cookies-next · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"In this new update '4.3.0,' the library started throwing a new error in production. I fixed the version to '4.2.1,' and the error was gone!"
2117-15fb04c807f265ba.js:1 TypeError: argument name is invalid
at t.serialize (8669-d0ad87f3fcb942d0.js:1:38692)
at t.setCookie (8669-d0ad87f3fcb942d0.js:1:42580)
at layout-d5ef98a14567a2c8.js:1:23308
at aW (fd9d1056-e1f8238183e3a8d9.js:1:73244)
at oe (fd9d1056-e1f8238183e3a8d9.js:1:84685)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:85323)
at or (fd9d1056-e1f8238183e3a8d9.js:1:85207)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:86268)
at or (fd9d1056-e1f8238183e3a8d9.js:1:85207)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:85303)
The text was updated successfully, but these errors were encountered:
I also stumbled on this issue. I used characters such as a semicolon in my key. Apparently, this is incompatible with the recent bump of cookies (#80).
"In this new update '4.3.0,' the library started throwing a new error in production. I fixed the version to '4.2.1,' and the error was gone!"
2117-15fb04c807f265ba.js:1 TypeError: argument name is invalid
at t.serialize (8669-d0ad87f3fcb942d0.js:1:38692)
at t.setCookie (8669-d0ad87f3fcb942d0.js:1:42580)
at layout-d5ef98a14567a2c8.js:1:23308
at aW (fd9d1056-e1f8238183e3a8d9.js:1:73244)
at oe (fd9d1056-e1f8238183e3a8d9.js:1:84685)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:85323)
at or (fd9d1056-e1f8238183e3a8d9.js:1:85207)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:86268)
at or (fd9d1056-e1f8238183e3a8d9.js:1:85207)
at ol (fd9d1056-e1f8238183e3a8d9.js:1:85303)
The text was updated successfully, but these errors were encountered: