we are not giving ourselves a deal of trouble merely forthe pleasure thereof

There is one more layer we can add, though

If you want a reference to the global object that works in any context, you can read this from a directly-called function. const global = (function() {return this})();. This evaluates to window in the browser, self in a service worker and global in nodejs.

I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.

This is the problem with baking in support for frameworks with special cases in the codebase. You can never support all the frameworks. :-(

There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.

According to our understanding of the inconsistencies, the feature was likely trying to support too many edge cases. All caching strategies have weaknesses and eventually break down if the usage is not properly scoped.