Jazor.LibNode.win-arm64 0.2.0

dotnet add package Jazor.LibNode.win-arm64 --version 0.2.0
                    
NuGet\Install-Package Jazor.LibNode.win-arm64 -Version 0.2.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Jazor.LibNode.win-arm64" Version="0.2.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Jazor.LibNode.win-arm64" Version="0.2.0" />
                    
Directory.Packages.props
<PackageReference Include="Jazor.LibNode.win-arm64" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Jazor.LibNode.win-arm64 --version 0.2.0
                    
#r "nuget: Jazor.LibNode.win-arm64, 0.2.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Jazor.LibNode.win-arm64@0.2.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Jazor.LibNode.win-arm64&version=0.2.0
                    
Install as a Cake Addin
#tool nuget:?package=Jazor.LibNode.win-arm64&version=0.2.0
                    
Install as a Cake Tool

Libnode: Node.js LTS for .NET

This project builds Node.js as a native shared library for embedding JavaScript in .NET applications, referencing and compatible with Microsoft's Node API for .NET.

  • Build the latest Node.js LTS with the embedding C API required by Microsoft's managed interop layer.
  • Load JavaScript packages and call JS APIs in the same process as a .NET application.
  • Reuse upstream native and managed tests to verify the compiled library.

The current build is Node.js v26.13.1 (Lithium LTS), verified with Microsoft.JavaScript.NodeApi 0.9.36. Source archives, commits and patches are pinned; builds do not resolve a floating latest version.

Version 0.1.0 is published for Linux x64 and Windows x64, with native, managed and actual NuGet consumer tests passing on both platforms. macOS builds remain future candidates. See the release.

Documentation

Minimal example — .NET calling JavaScript

Reference Microsoft.JavaScript.NodeApi 0.9.36 and Jazor.LibNode 0.1.0. The latter provides the native runtime, serving the same role as Microsoft.JavaScript.LibNode. Reference one native runtime package in the application.

dotnet add package Microsoft.JavaScript.NodeApi --version 0.9.36
dotnet add package Jazor.LibNode --version 0.1.0

NodeApi resolves the appropriate native library from the package automatically:

using Microsoft.JavaScript.NodeApi;
using Microsoft.JavaScript.NodeApi.Runtime;

using var platform = new NodeEmbeddingPlatform(new NodeEmbeddingPlatformSettings());
using var runtime = platform.CreateThreadRuntime();
runtime.Run(() =>
{
    var answer = (int)JSValue.RunScript("21 * 2");
    Console.WriteLine(answer); // 42
});

Create one platform per process. Dispose its runtimes before disposing the platform. For module imports, async calls and errors, see the tested NuGet consumer.

Packages

The package projects produce native runtime assets without adding another managed interop layer:

  • Jazor.LibNode — metapackage for the complete set of validated runtime packages.
  • Jazor.LibNode.<rid> — platform library under runtimes/<rid>/native/, with source/build metadata and licenses. Published 0.1.0 supports linux-x64 and win-x64; the 0.2.0 release catalog adds linux-arm64 and win-arm64 after verification.

The Linux development candidate passes 60 native embedding cases, 22 Microsoft embedding/GC tests, 38 separate mock tests, and an isolated consumer using the actual Microsoft NodeApi NuGet package. The local binary requires glibc 2.39 and GLIBCXX 3.4.32; older distributions need a separate build and validation.

Windows x64 passes the same 60 native, 22 embedding/GC and 38 separate mock cases, plus the actual NodeApi NuGet consumer on Windows Server 2022. Install the Microsoft Visual C++ 2015–2022 x64 Redistributable for its VC runtime dependencies. The tested Windows .NET host uses <CETCompat>false</CETCompat>; see the upstream issue audit for the managed-layer limitations.

Candidate packages are generated under artifacts/packages/; see development instructions to reproduce them.

Development

For building, testing and packaging, see README-DEV.md. The Linux candidate workflow builds from source or imports a verified local build, then repeats upstream compatibility tests, NuGet consumers and issue regressions and preserves their reports. Importing a local build skips V8 compilation. Release tags publish the verified package set through GitHub Actions, using NuGet trusted publishing. See the release guide for setup and dry runs.

License

Build and packaging code is licensed under the MIT License. Native distributions include Node.js and embedding-source licenses and third-party notices. See NOTICE.txt for source attribution.

This is an independent build, not a Microsoft release.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Jazor.LibNode.win-arm64:

Package Downloads
Jazor.LibNode

Node.js LTS native embedding runtime for Microsoft.JavaScript.NodeApi.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.2.0 198 11/17/2026