next-auth: Maximum call stack size exceeded in logger
Describe the bug I get this error only in version 3.15.1
Uncaught RangeError: Maximum call stack size exceeded
at Object.warn (logger.js:23)
when the user is signed in
Steps to reproduce Just login
Expected behavior Should load the page
Screenshots or error logs
Uncaught RangeError: Maximum call stack size exceeded
at Object.warn (logger.js:23)
Feedback Documentation refers to searching through online documentation, code comments and issue history. The example project refers to next-auth-example.
- Found the documentation helpful
- Found documentation but was incomplete
- Could not find relevant documentation
- Found the example project helpful
- Did not find the example project helpful
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 15 (8 by maintainers)
Commits related to this issue
- https://github.com/nextauthjs/next-auth/issues/1783 のエラーになったのでupdateして解決 — committed to shibayu36/next-prisma-auth-tutorial by shibayu36 3 years ago
🙏 For anyone interested, here was the problem 🤦, totally unintentional:
I have no time to provide a reproduction now but I can tell you that, commenting out the content of the
warnfunction in thesrc/lib/logger.jsfile, solves the issue.@SeanGroff it should be out, under
3.15.4. Could anyone see if the problem is fixed now and report back ASAP?Working out some kind of a release issue, hopefully will be resolved soon. Thanks for your patience 🙏
@balazsorban44 wow, really appreciate this fix and your work. It’s back to normal at least for me.
I can report back as soon as 3.15.2 is released. I’m not seeing 3.15.2 released quite yet.
So since several people have reported it, I tried to reproduce it myself, but did not manage. I decided to revisit the last release(s), and found I tiny change, that just seemed very odd, probably introduced by being clumsy, in
3.15.0. 🤷 so I reverted it, but since I cannot reproduce the issue, could someone in this thread verify that this has been indeed fixed in3.15.2when it is out?@ramiel @followbl @jahirfiquitiva @4ortytwo