Servus! If you ship Kotlin/Wasm and have ever ope...

# webassembly

[Vasily Levchenko]

Servus!

If you ship Kotlin/Wasm and have ever opened the resulting .wasm to see what the
backend actually emitted, this might save you a trip to the CLI. New in Hexana for
JetBrains IDEs 0.11.1:

Kotlin/Wasm modules are recognized automatically. Detected
modules get a Kotlin/Wasm badge on the Functions tab and in the virtualized WAT view.

Click a function’s badge to jump to its Kotlin source declaration. The mapping comes
from the plain fully-qualified names the Kotlin/Wasm backend writes into the name section.

Compare two `.wasm`modules:*Compare WASM With…*(project-view context menu or Tools menu) opens a diff editor. The*Size Impact*tab shows per-section and per-function byte deltas sorted by impact; the*Entities*tab classifies every entity kind (imports, exports, functions, globals, tables, memories, types, data and element segments) as added / removed / modified / moved, with a supply-chain banner that highlights newly-introduced imports (host namespaces such as`env`/`wasi_*`are flagged). Functions are matched structurally (content hash + call graph), so renaming or renumbering does not show up as spurious churn. Selecting a function opens an on-demand side-by-side WAT comparison rendered with symbolic names — so an unchanged caller of a renumbered function reads identically — with standard red/green line-level highlighting. Table rows are colour-coded by change kind, with aligned columns


JetBrains Marketplace: https://plugins.jetbrains.com/plugin/29090-hexana
Docs: https://jetbrains.github.io/hexana

Gott schütze Bayern!