Your project looks really interesting. I've been looking into many different "plugin" architecture options (mainly with the goal to run untrusted js/ts code) and your extended readme sounds interesting.
But i can tell it's early so i'm not fully seeing how this would be used (like an example folder).
- I too have tried to think of how plugins could be "full-stack" with both sandboxing on BE & FE via iframe but i'm not seeing in your repo the code that handles the FE sandboxing? (I could be totally looking in the wrong place)
- I looked into using wasm "containers" as well- does your architecture have a scalable way to optimize "cold boot" of a container for near-instant run/render?
Again, cool project and good luck! I think there's so much room for innovation in this area of making micro-functionality truly portable & composable!
yeah making core framework in fast low level language and making scripting/embed language on top is such underexplored area i think.
i have removed suborigin bashed frontend sandbox for now, inline iframe is just faster to iterate, i will bring back suborigin later.
iframe related code would here.
It's about 3 months in the making and needs improvements around ops, tests. I am hoping to make progress with adding tests in the coming days and provide monitoring capabilities.
But i can tell it's early so i'm not fully seeing how this would be used (like an example folder).
- I too have tried to think of how plugins could be "full-stack" with both sandboxing on BE & FE via iframe but i'm not seeing in your repo the code that handles the FE sandboxing? (I could be totally looking in the wrong place)
- I looked into using wasm "containers" as well- does your architecture have a scalable way to optimize "cold boot" of a container for near-instant run/render?
Again, cool project and good luck! I think there's so much room for innovation in this area of making micro-functionality truly portable & composable!