-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: Enable consoleLoggingIntegration
by default in node, bun, cloudflare, and vercel-edge sdks
#17747
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
base: develop
Are you sure you want to change the base?
Conversation
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
if (options.enableLogs) { | ||
// TODO(v11): Remove this once we add logs to the `consoleIntegration`. | ||
integrations.push(consoleLoggingIntegration()); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no action required: Not sure if it makes sense to unify consoleIntegration and consoleLoggingIntegration. Probably depends on our plan for breadcrumbs going forward but I kinda like smaller single-purpose integrations over larger ones.
This enables the console logging integration by default in node, bun, cloudflare, and vercel-edge sdks. By enabling it in the node sdk, we also enable it in the aws serverless and google cloud function sdks.
In v11 we can refactor this as we'll use the
consoleIntegration
to handle this. See #17702 for more details.