Replies: 2 comments 1 reply
-
|
Thanks for sharing this. Let me check with our docs team. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@Sajith15 I have checked internally. Please feel free to submit a PR and our team will review. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature or potential improvement
Context:
The Langfuse TypeScript SDK was completely rewritten in v4 (August 2025), moving to an OpenTelemetry-based architecture. This is a significant breaking change from v3. Based on the GitHub Discussions, several teams are hitting friction migrating, particularly around:
@langfuse/otelpackage andLangfuseSpanProcessorsetupcryptomodule not available - see discussion 🚀 Langfuse TypeScript SDK v4 is here #8403)langfuse.trace()+trace.generation()calls to the new OTel span modelWhat I want to write:
A
MIGRATION_V3_V4.mddocument (or a new docs page) covering:Section 1 - Core SDK migration
Side-by-side before/after for every major pattern:
langfuse.trace()→ v4 OTel span model)langfuse.score()→ v4 equivalent)await langfuse.shutdownAsync()- unchanged)Section 2 - Framework integrations
Before/after for:
observeOpenAI()Section 3 - Platform-specific gotchas
cryptounavailable - workaround: use Node.js runtime for instrumentation)Section 4 - Self-hosted Docker upgrade path
I've gone through the migration myself and hit most of these issues. This guide would have saved me several hours. Is this a PR the docs team would accept? I can also include runnable code examples in a GitHub Gist I can link from the guide.
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions