svelte/internal question -- migration from v4 to v5

[michaelcmelton]

Describe the bug

• Svelte version: 4.2.19
• Function in question from svelte/internal: get_current_component

Some context - We're using this function to gather a reference to the parent html element to allow us to get access to the dispatchEvent to send CustomEvents. Pattern below:

// inside a class constructor for a separate eventing abstraction for side effects
    this.webComponent = get_current_component();

// ... other irrelevant code

// inside emit event function
    const detail = this.getEventDetail(eventName, eventDetails);

    const isReactNative = 'ReactNativeWebView' in window;
    const iFrame = !(window === window.parent);

    if (this.webComponent) {
      this.webComponent.$$.root.ownerDocument.dispatchEvent( // this is what we're looking to replace in v5.

Reproduction

No repro -- just a question

Logs

System Info

N/A

Severity

blocking an upgrade

[MotionlessTrain]

The name webComponent for that variable confuses me whether this is a custom element in svelte, or another svelte component, or something other than a svelte component which happens to be loaded from within svelte.
Depending on that, the answer could be different

[michaelcmelton]

It's a custom element, sorry. I should have made that specific.

[MotionlessTrain]

In that case, you can use the $host rune to reference the html element

[michaelcmelton]

Sorry, I should really be more specific. 😅 The webComponent variable is the custom element. The context in which this dispatchEvent is ran happens within a .ts file which happens to be loaded from within Svelte.

[MotionlessTrain]

Is the class created from the svelte component?
In that case, you may be able to pass $host() to the constructor of the event emission class