win
win
Thank you, I will test it :)
I define above problem is "**How to select the best method overload from js args**"
I'm fixing _'How to select the best method overload from js args'_ early preview will release soon
@dpwhittaker see preview code and detail in => https://github.com/prepare/Espresso/commit/b27cfe4a055c4ee9a087537e565b0d90ff1f76a5 ---  _pic 1: compare between pure .net (blue box) and Espresso (red box), correct method selection_ **THIS IS EARLY PREVIEW**...
clean up, see=>https://github.com/prepare/Espresso/commit/b27cfe4a055c4ee9a087537e565b0d90ff1f76a5
/lib/internal/modules/cjs/loader.js about line 848 ```javascript Module._resolveFilename = function(request, parent, isMain, options) { if (StringPrototypeStartsWith(request, 'node:') || NativeModule.canBeRequiredByUsers(request)) { return request; } //////////////////////////////////////////// //#espresso, #4 if (request.endsWith(".espr")) { return request; }...
file /lib/internal/main/run_main_module.js line 9 ```javascript markBootstrapComplete(); ////////////////////////////////// //#espresso, #6 ///////////////////////////////// if (typeof LibEspresso !== 'undefined') { //we use our lib espr LibEspresso require('internal/modules/cjs/loader').Module.runMain("hello.espr"); return; } ///////////////////////////////// ``` patch 6: /lib/internal/main/run_main_module.js
> The reason why I ask is because I think this could potential allow running javascript code in .NET that actually utilize network/file and node_modules. 👍 I 've test it,...
> Are you compiling all of nodejs, but only exporting the V8 functions you need? In this Espresso repo, we use v8 from nodejs, _but It not include any function...