Is it possible to make the embedder API opaque regarding Chromium STL?

30 views
Skip to first unread message

Louis Poirier

unread,
Oct 13, 2026, 3:23:28 PMOct 13
to v8-dev
Hello v8-dev,

Currently, I'm able to build v8_monolith target for Linux and Windows (x86_64) without Chromium STL. It allows linking the static library with MSVC on Windows for example.
See repository with workflows: https://github.com/poirierlouis/v8-nocr

Though, I can't enable the sandbox feature of V8. As far as I understand, Chromium STL and custom compiler as dependencies of V8 repository are required for the sandbox feature. As in, its part of the core and a requirement to safely manage memory in the sandbox.

Would it be possible for API embedders to only be exposed to non-STL types (unique_ptr -> V8::UniquePtr, shared_ptr -> v8::SharedPtr, vector -> v8::Vector)? If V8 encapsulates and provides the user with opaque types, then there shouldn't be mixing STL issues anymore at linking time?

I'm likely missing parts of the whole picture, so I'm eager to get your insight about this idea. And if it seems possible technically.

Ideally, it should allow compilation of the static library (monolith) as-is with all Google/Chromium toolchain, dependencies... while linking with other STL / compilers to benefit from all V8 features without compile/link/runtime errors.

Looking forward to your feedback.
Reply all
Reply to author
Forward
0 new messages