I could be wrong, but I think any ES modules that run in the browser also run on Deno. You only hit problems when using CommonJS, which neither Deno nor the browser understand natively.
There is a chapter of the Deno docs on Node compatibility if you're interested.
But really, the question is... what are you trying to do? I don't know the use cases for the Deno bundler all that well. Deno always struck me as a backend thing, whereas for frontend bundling I tend to use Vite or Snowpack.
>You can separate them and communicate via iframes
, React, Vue, Angular, Web Components, Polymer, or really any way you can imagine and the browser allows.
The problem here is that , given that we are looking at decoupled (from component tree structure) ways of state sharing between components of random place in the component tree , in an app that has only shadow DOM components , I can comprehend only the iframes
way .
Is this [1]:
>In React, sharing state is accomplished by moving it up to the closest common ancestor of the components that need it.
what you are trying to say here :
>You have 2 things you're trying to separate: the state of your multi-my-app view and the state inside of the my-app component. my-app doesn't have to care what data it works on, but the parent working with several my-apps has to manage giving them the correct data.
?
>but the parent working with several my-apps has to manage giving them the correct data.
It would be interesting to show me (or give me some links) how that can happen given the conditions that I mentioned in the first paragraph of this comment . How would you do it with redux for example ? Or how would you do it with react for example ?