Resolve sourcemaps from captured frontend stack frames client side
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
If sourcemaps are actually referenced in the JS files but are only resolvable behind a corporate VPN, it would be cool if HyperDX could resolve these client side in the browser.
I suggested an approach here https://discord.com/channels/1149498480893640706/1149500035403350036/1449055230577873130
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how captured frontend stack frames and referenced JS files are handled in the browser; review the linked Discord discussion for the proposed approach. Done means sourcemaps reachable only through the user's corporate VPN can be resolved client side.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100