so you just need a blob.py
True that, you need basically some code that your eval function can understand. Klipse does this already, the whole infrastructure is built in cljs but then everything that compiles to js can be evaluated in the browser.
The additional step to add to the upgrade is the transpiler, call a function to convert to js before eval and call a function for converting back the result I guess
Are you talking about clj-cljs or js-cljs?
I'm confused each time you mention a transpiler
Sorry this is cljs-in-cljs and a transpiler example would be the BuckleScript one converting from ocaml to js
So the idea is to have Lumo or a fork as universal repl for the whole js ecosystem
Just noticed Unrepl in this case stands for universal repl 😀
It is probably better for me at some point to create a poc or something, I hope to get a bit of time soon
so to expand: the repl receives a function, the repl transpiles to js, the repl evals the js. Of course there should be a mechanism to discover the function that does the transpilation to js...it would be awesome if we could send it as blob but it might a fully library
in case of Bucklescript, this whole thing: https://www.npmjs.com/package/bucklescript
I agree this might be a bit out of scope here
How easy it is to hook up in nodejs module resolution?
(If I understand the question correctly) In lumo
the module resolution is done automatically, node.js takes care of it so whatever is in .node_modules
gets resolved on a require
.