Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(node): Support Node 26#20710
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
Uh oh!
There was an error while loading. Please reload this page.
feat(node): Support Node 26 #20710
Changes from all commits
0aedb54c92d5554616643376aed93f508b4259187fdf6b7c035b031af481b9fe41907df1fc10bf757d175b19a2041565f9304af64f73ad06File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -639,7 +639,7 @@ class ContinuousProfiler { | ||
| /** Exported only for tests. */ | ||
| export const _nodeProfilingIntegration = ((): ProfilingIntegration<NodeClient> => { | ||
| if (![16, 18, 20, 22, 24].includes(NODE_MAJOR)) { | ||
| if (![16, 18, 20, 22, 24, 26].includes(NODE_MAJOR)) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Profiling warning message omits Node 26 from supported listMedium Severity The version check on line 642 was updated to include Reviewed by Cursor Bugbot for commit f73ad06. Configure here. | ||
| consoleSandbox(() => { | ||
| // eslint-disable-next-line no-console | ||
| console.warn( | ||
Uh oh!
There was an error while loading. Please reload this page.


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.
Bug: The Lambda-specific console instrumentation
instrumentConsoleLambdabypasses configured filters, causing all console messages to be captured as breadcrumbs regardless of the filter settings.Severity: LOW
Suggested Fix
Update the
instrumentConsoleLambdafunction to apply the filters stored in the_filterset before callingtriggerHandlers. The implementation should check if a console message matches any of the filters and, if so, prevent it from being captured.Prompt for AI Agent
Did we get this right? 👍 / 👎 to inform future reviews.