Should we let contributions opt into a stable perf label? (perf-measurement names break in prod builds)

[ankitsharma101]

Idea Description

While profiling frontend startup, I ran into something that might be worth
discussing more generally: perf labels for contribution lifecycle hooks
(initialize/configure/onStart) are just contribution.constructor.name.

That works fine in dev, but in a minified production build the bundler mangles
class names, so the labels turn into unreadable garbage — right when you'd most
want trustworthy perf data.

A couple of directions come to mind, and I'm not sure which is better:

1. Let contributions opt into a stable label via something like an optional
   perfId field, falling back to constructor.name when unset.
2. Just stop minifying class names in the first place — most bundlers support
   this (e.g. Terser's keep_classnames, esbuild's keepNames). This would fix
   it for every contribution automatically, no API change needed, though it
   presumably makes the bundle very slightly larger and affects all classes,
   not just contributions.

Curious what people think — is this worth solving at the build level, or is an
opt-in API cleaner? Happy to put together a PR either way once there's some
direction.

[github-actions[bot]]

Hi @ankitsharma101, thanks for starting this discussion! 👋

The Theia community will take a look soon. In the meantime, you might find helpful information in:

• 📖 Theia Documentation
• ❓ FAQ
• 💬 Previous Discussions

---

💙 Eclipse Theia is built and maintained by a community of contributors and sponsors. If Theia is valuable to your work, consider sponsoring the project. For professional support, training, or consulting services, learn more about available options.