Under the hood
Useful2 Signal3
Plugin hook calls now carry a caller chain, so a call can be traced to what triggered it.
What's wrong with this entry?
Anonymous. No account, no email.
What
The worker that runs plugin hooks dropped its own bookkeeping for message ports, pending replies and counters in favour of shared helpers, and its messages now carry which side is serving plus a caller chain, so a call into a plugin interface can be attributed to what triggered it.
Details
- Unhandled promise rejections in the worker are now picked up by a shared handler.
- Callers are passed alongside a call identifier into the interface dispatch.
- Unloading still reports through the existing message about the plugin's environment being unloaded.
Evidence
the plugin's environment is unloaded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.