ClearScript Library

Results 87 comments of ClearScript Library

Hi @nextfool, Yes, unfortunately, the Chromium team's build scripts are very finicky, particularly on Windows, as that's not their primary platform. We'll see if we can reproduce this, and if...

Hi @grumpydev, Thanks for your contribution! >It also appears that using "Invoke" doesn't check or use the awaitDebuggerAndPause flag Quite correct. In fact, ClearScript provides many ways to enter V8's...

Hi @KurtGokhan, We have no mobile plans for ClearScript at the moment. As you probably know, ClearScript is a side project, and supporting the three major desktop platforms – including...

Hi @KurtGokhan, Thanks for reporting this. We're considering making OS/platform detection overridable in a future release. Cheers!

Hello @ColonelBundy, >Swapping out or providing the ability to swap Newtonsoft for System.Text.Json is highly desirable due to performance reasons. Outside of test code, ClearScript currently uses Newtonsoft.Json only for...

Hi @ColonelBundy, >Yes I'm referrrning to the [`EnableStringifyEnhancements`](https://microsoft.github.io/ClearScript/Reference/html/T_Microsoft_ClearScript_V8_V8ScriptEngineFlags.htm) feature. We looked into `System.Text.Json` but went with Json.NET due to the latter's universal compatibility. It's likely that we'll drop support for...

Hi @SeanMsi, We've reproduced the issue with ClearScript 7.2 on Alpine in WSL. For us, ClearScript 7.0 with `gcompat` doesn't work either, failing quietly as soon as we try to...

Hi @William-Froelich, Thanks for looking into this. >That make it seem to be related to threading not running | being supported | not detected at runtime. Hmm, [`std::call_once`](https://en.cppreference.com/w/cpp/thread/call_once) is a...

Hi @William-Froelich, Thanks for investigating this! >`none of [/workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python] matched specification 2.7.0` Not sure what's going on there. On Ubuntu LTS, that path is Python 2.7.18. What happens when you...

Yeah, the V8 build process is finicky about its platform. For example, all 32-bit versions must be cross-compiled. Apparently, it's now using its own glibc-based Python.