Closed academo closed 1 year ago
I kept experimenting with this and the only way I found to make sourcemaps work was to make sure the sourceMappingURL
has either an absolute url or relative to the website hostname. If the sourcemap is (as normally is) relative to the script you are trying to execute it won't load it.
hello.
I am experimenting with near-membrane to isolate plugins executions.
I am using near-membrane-dom to load the plugins code, I create a virtual environment, load the code in a string and use
evalute
to get the code executed.Uncaught Proxy(Object) {}
Do you know a good way to unwrap this object to present it human-readable?Generally speaking, is there a way to get what line of code generated the error inside the virtual environment? or maybe there's another way to evaluate the plugin's code that doesn't rely on a string so meaningful errors can be generated? There is little to none documentation and I feel force to ask here
Thanks in advance and amazing work in this library.