Release 6.3.7

[devin-ai-integration]

Description

Removes all Sentry integration from the TypeScript SDK to resolve Deno compatibility issues in Supabase Edge Functions. The original error TypeError: The URL must be of scheme file was caused by Sentry's profiling module (@sentry/profiling-node) attempting to use Node.js-specific file URL schemes that are incompatible with Deno runtime.

Related Issue: User reported inability to use @langtrase/typescript-sdk@6.3.5 in Supabase Edge Functions due to Sentry profiling module failures.

Changes Made

Core Changes

• Removed Sentry imports from src/init/init.ts:

  • import * as Sentry from '@sentry/node'
  • import { nodeProfilingIntegration } from '@sentry/profiling-node'
  • import { SENTRY_DSN } from '@langtrace-constants/common'

• Removed Sentry initialization block including:

  • Sentry.init() configuration with profiling integration
  • Custom beforeSend filter for LangtraceSdkError
  • Context setting with SDK initialization options
  • Global process error handlers for unhandled rejections and uncaught exceptions

• Removed SENTRY_DSN constant from src/constants/common.ts

• Removed LANGTRACE_ERROR_REPORTING environment variable handling

Dependencies

• Removed from package.json:
  • @sentry/node: ^8.30.0
  • @sentry/profiling-node: ^8.30.0
• Updated package-lock.json via npm install (1619 lines removed)

Documentation

• Removed "Error Reporting to Langtrace" section from README.md that documented LANGTRACE_ERROR_REPORTING=False environment variable

Verification Steps Completed

✅ npm run lint - No linting errors
✅ npm run build - TypeScript compilation successful
✅ Comprehensive search for remaining Sentry references - None found in src/
✅ Git commit shows 5 files changed, 242 insertions(+), 1619 deletions(-)

⚠️ Breaking Changes

• LANGTRACE_ERROR_REPORTING environment variable is now ignored (previously defaulted to 'True')
• No error reporting mechanism - SDK will no longer capture or report unhandled errors
• Global error handlers removed - unhandled promise rejections and uncaught exceptions will not be automatically captured

Human Review Checklist

Critical Items:

• Test in actual Deno environment - Verify the original Supabase Edge Functions error is resolved
• Consider error reporting strategy - Evaluate if complete removal vs. Deno-compatible alternative is preferred
• Breaking change impact - Assess if any existing users depend on LANGTRACE_ERROR_REPORTING functionality
• Verify complete removal - Double-check no Sentry references remain in codebase

Standard Review:

• Code changes look correct and complete
• Documentation updates are appropriate
• Dependencies properly removed from package.json
• No unintended side effects from removing global error handlers

---

Link to Devin run: https://app.devin.ai/sessions/41ba048c88d14ed2928fc83b587cf5b9
Requested by: karthik@scale3labs.com

Note: This is a complete removal approach rather than conditional Deno detection. Consider if a more nuanced solution (e.g., runtime detection to disable only problematic Sentry features in Deno) would be preferable for maintaining error reporting in Node.js environments.

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring