trunk-rs/trunk

Proposal: Generating source map files for WASM files

Open

#851 opened on Aug 12, 2024

View on GitHubContributor guide
 (3 comments) (5 reactions) (0 assignees)Rust (315 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (4,347 stars)
PR merge metrics
 (PR metrics pending)

Description

I believe that having a proper way to track down stack traces into Rust code in browser DevTools. I've found this tool that generates a .map file that the browser can use to match js and wasm to rust code: https://github.com/mtolmacs/wasm2map. This tool can be used as a library or a CLI tool.

Proposal

Embed wasm2map in trunk, and adding a new step that generates the .map file to allow the browser devtools to correlate stacktrace addresses with rust source code file and lines.

Contributor guide

Research direction
Examine how trunk processes WASM files and understand the build pipeline to integrate wasm2map for .map generation.
Tech stack
rust
Domain
web devtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustWASM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60