Strange behavior while importing react

[thebergamo]

I have a different use case, where I build my SSR react entry-server.tsx using Vite (either with noExternals or with externals), then try to dynamically import it into Deno, but what happens is that it while processing the output from esbuild it doesn't find some React part, for instance useState that is being used by some component.

Not sure if esbuild is treeShaking my files the output in this case, but in any case I can't correctly import my module. Any advice?

[thebergamo]

From my current discoveries, it seems that React is getting imported twice and that might be the reason that is causing this issue.
As my entry-server.tsx exports export a react component I marked it as external inside vite, but while importing it using this module, inside Deno Deploy it seems to be importing it again and bundling it. Is there any way to avoid importing and bundling this?

Locally it is working now, only in Deno Deploy it is having this issue with duplicated React version