-
Notifications
You must be signed in to change notification settings - Fork 346
Open
Labels
Description
Problem
When using the latest version of HyperDX (v2), there's no way to upload JavaScript source maps. The @hyperdx/cli upload-sourcemaps command only works with the HyperDX Cloud (v1), as it requires the /api/v1/sourcemaps/upload-presigned-urls endpoint.
This means frontend errors captured via @hyperdx/browser SDK show minified stack traces, making debugging difficult.
Current Behaviour
npx @hyperdx/cli upload-sourcemaps \
--serviceKey "..." \
--apiUrl "https://my-clickstack-instance" \
--path .next
# Fails because HyperDX doesn't have the sourcemap upload APIExpected Behaviour
HyperDX deployments should support source map uploads, either:
- Built-in storage within HyperDX (e.g., storing source maps in ClickHouse or a configurable S3-compatible storage)
- Client-side source map resolution (as suggested in Resolve sourcemaps from captured frontend stack frames client side #1501)
- Documentation for self-hosting the source map API component
Use Case
We're using HyperDX v2 for observability. We have a SvelteKit frontend instrumented with @hyperdx/browser for session replay and error tracking. Without source maps, stack traces in captured exceptions are unreadable.
Environment
- Deployment: ClickStack on ClickHouse Cloud
- Frontend: SvelteKit with
@hyperdx/browserSDK - Build tool: Vite (generates
.js.mapfiles)
Related
- Resolve sourcemaps from captured frontend stack frames client side #1501 - Client-side source map resolution proposal