Sam Cao
It's more like a JS trick as follows. ```java nodeRuntime.allowEval(true); nodeRuntime.getExecutor("const vm = require(\"node:vm\");\n" + "const script = new vm.Script(\"eval('1+1')\");\n" + "console.log(script.runInThisContext());\n" + "console.log(script.runInNewContext(vm.createContext({eval})));").executeVoid(); // Output 2 2 ```
Those API require certain understanding on how V8 works internally. Please let your code.
It doesn't seem to be a complete reproducible code. Could you leave a repo with the issue?
I guess you misunderstood how a thread pool works.
Please review the docs, best practices and unit test.
Script, Module, Function all support code cache. Please refer to JavaDoc for detail. Javet gives almost all possibilities to the app. It's app's decision on what native workers are, how...
1. Javet provides Node.js mode. 2. Polyfill work is in project Javenode. 3. One of the goals is to provide genuine Node.js and V8 to the Javet users.
Please try `NODE_FLAGS`.
Do you think `1` or `2` is realistic?
Please leave a repo with the issue.