A V8 adapter implemention of the JSI interface for the react-native framework.
- Download and Install
Windows 10 Windows SDK:
https://developer.microsoft.com/en-us/windows/downloads/sdk-archive
Note: Windows SDK has to be Windows 10 version, NOT Windows 11 - Download and Install
Microsoft Visual C++ Redistributable x64
Microsoft Visual C++ Redistributable x86
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist - Download and Install
Visual Studio 2022
https://visualstudio.microsoft.com/vs
In Visual Studio Setup, Select the following Individual Components:- MSVC v143 - VS 2022 C++ x64/x86 Spectre-mitigated libs (Latest)
- C++ ATL for latest v143 build tools with Spectre Mitigations (x86 & x64)
- The Visual Studio C++ Clang Compiler for Windows component
(
Microsoft.VisualStudio.Component.VC.Llvm.Clang). The build uses its libclang to embed the API manifest inv8jsi2.dll(seetools/stela/README.md), and the sandbox build (scripts/sbox-build.ts) compiles with its clang.
From the repo root, check and install NASM, an accepted Python, and Node.js 24+:
powershell.exe -NoProfile -File .\scripts\install-prerequisites.ps1The script asks once before installing missing tools through WinGet; -CheckOnly
reports without installing, and -Yes consents and accepts WinGet agreements
(installer/UAC prompts may remain). Existing accepted tools are kept.
WinGet is needed only to install missing tools.
If PowerShell blocks execution, consult Microsoft's
execution-policy documentation
and your organization's policy. The script does not change policy.
It does not install Visual Studio C++/Clang, the Windows SDK, or Git.
The supported build uses vendored Node.js 26.x sources through
dev.ps1 / scripts/build.ts. Outputs are
v8jsi2.dll, v8jsi_test.exe, and node_api_tests.exe in
deps/nodejs/out/{Release,Debug}/, packaged as Microsoft.JavaScript.V8.
dev.ps1 at the repo root is the canonical entry point for
the supported build. Run .\dev with no arguments to see available commands.
Build (Release x64 by default):
.\dev buildOther configurations:
.\dev build --configuration debug
.\dev build --platform x86
.\dev build --platform arm64Build + run tests:
.\dev build --testRun the fork-sync tool (sync vendored Node.js / asio from upstream):
.\dev fork-sync --dep nodejs --statusNode.js syncs use snapshot mode with keepLocalDeletions to preserve the
pruned build closure. For a branch change, set the tracking branch in
deps/nodejs/sync-config.json before starting, but retain its old base commit.
Pass both the release tag and its peeled commit SHA to pin an annotated tag:
.\dev fork-sync --dep nodejs --tag <tag> --commit <sha>.
Without --mergetool, unresolved conflicts pause for manual resolution.
A dedicated sync worktree and its .sync cache can be reused on fresh branches
once the previous changes are committed and the worktree is clean.
See .\dev build --help and .\dev fork-sync --help for the full
option set. The build command forwards to
scripts/build.ts, which drives
deps/nodejs/vcbuild.bat with narrow-build
flags (skips node.exe, cctest, embedtest, etc.). See
CLAUDE.md for the underlying details.
.\dev build also runs a version-sync check that compares
config.json.nodejs_version against the vendored Node.js version in
deps/nodejs/src/node_version.h, and fails fast on mismatch. See
docs/versioning.md for the 26.x.y policy.
Until the JSI headers find a more suitable home, they're currently duplicated between the various repos. Code in jsi\jsi should be synchronized with the matching version of JSI from react-native (from https://github.com/facebook/hermes/tree/master/API/jsi/jsi).
For the experimental Windows sandbox client API, see Sandboxed JavaScript through v8sbhost.dll.
See Contributing guidelines for how to setup your fork of the repo and start a PR to contribute to React Native V8 JSI adapter.
The V8 JSI adapter, and all newly contributed code is provided under the MIT License. Portions of the JSI interface derived from Hermes are copyright Facebook.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.