Why does the "reactivity" get lost after passing the signal to a Solid component imported via UMD?

[SaekiRaku]

Reproduction repository：https://github.com/SaekiRaku/why-solid-not-reactive-when-use-umd

I bundled a Solid component into an UMD module, and import it in a vite project. I used it like this:

const [value, setValue] = createSignal(0)

return <div>
    <SimpleUMDSolid outside={value()} />
    <button onClick={()=>{ setValue( value() + 1 ) }}>Increase</button>
</div>

But inside <SimpleUMDSolid />, trying to render () => props.outside won't change the value after clicking the Increase button.

🙏Please help, thanks.

[SaekiRaku]

I figured it out by myself. I need to configure solid-js in externals and then provide the solid-js dependency/instance used in the vite project when importing. I misunderstood that solid-js compiles reactive operations into dom operations, mistakenly thinking that all operations are compiled and there's no need for an independent runtime like React. It seems that solid-js shares some context in terms of signals to achieve reactivity, so the same solid-js instance must be used.