Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(logger): attempt at fixing infinite loop #1789

Merged
merged 1 commit into from
Apr 20, 2021

Conversation

balazsorban44
Copy link
Member

What:

change clientLogger to {}

Why:

In 3.15.0, an {} have somehow accidentally been replaced by console

How:

🤷

Checklist:

  • Documentation
  • Tests
  • Ready to be merged

Fixes #1783

@vercel
Copy link

vercel bot commented Apr 20, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/ESivjGECX44mD9s1sH3xxznRsPUB
✅ Preview: https://next-auth-git-fix-logger-infinite-loop-nextauthjs.vercel.app

@github-actions github-actions bot added the core Refers to `@auth/core` label Apr 20, 2021
@balazsorban44 balazsorban44 merged commit 2becdad into main Apr 20, 2021
@balazsorban44 balazsorban44 deleted the fix/logger-infinite-loop branch April 20, 2021 19:22
@github-actions
Copy link

🎉 This PR is included in version 4.0.0-next.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Refers to `@auth/core`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maximum call stack size exceeded in logger
1 participant