Dynamically importing a module loses "ownership"... (but not in the Solid playground)

[AlexErrant]

This is gonna be a weird one.

I'm building an app that allows 3rd party code to be loaded as plugins. This code will be loaded dynamically, e.g.

  const script = `import {...} from 'solid-js'` // rest of code omitted for brevity
  const blob = new Blob([script], { type: "text/javascript" });
  const url = URL.createObjectURL(blob);
  const module = await import(url);

Here's it working in the Solid playground, as evidenced by Plugin owner being not null in the console.log output. Note the plugin's count and the ChildComp's count are both reactive.

Describing the code:

• pluginCode represents 3rd party code dynamically loaded by import. It uses the low-level template and insert SolidJS helpers.
• loadPlugin loads the pluginCode into a module and returns the plugin
• ChildComp is a nested child component. The DOM hierarchy is App, which contains the 3rd party plugin, which contains ChildComp. This demonstrates that 3rd party code can contain SolidJS components defined by the parent and retain reactivity.
• App, which loads the 3rd party code using <Dynamic>

However, the plugin doesn't have an owner when used in a minimal Vite app with identical code as evidenced in this Stackblitz. The console.log reveals that Plugin owner is null, and the plugin's count is not reactive. (Strangely, the ChildComp has an owner and retains reactivity.)

I've tried downgrading to the version of Solid used by the playground, dev and preview builds, and runWithOwner, but nothing works.

How can I get the plugin to have an owner like in the Playground?

[AlexErrant]

Ah derp. I needed

    rollupOptions: {
      external: [
        "solid-js"
      ]
    },

and to run it in production mode... which I wrote about a year ago. Ulgh.