Support Source Map Uploads in HyperDX v2

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 API

Expected Behaviour

HyperDX deployments should support source map uploads, either:

1. Built-in storage within HyperDX (e.g., storing source maps in ClickHouse or a configurable S3-compatible storage)
2. Client-side source map resolution (as suggested in #1501)
3. 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/browser SDK
• Build tool: Vite (generates .js.map files)

Related

• #1501 - Client-side source map resolution proposal

Start with the @hyperdx/cli upload-sourcemaps command, its /api/v1/sourcemaps/upload-presigned-urls dependency, and the client-side source map resolution proposal in #1501. Compare the current HyperDX v1 flow with the ClickStack deployment described here, then define which v2 upload or resolution path is supported and verify that Vite-generated .js.map files produce readable @hyperdx/browser stack traces.