Skip to main content
Jering.Javascript.NodeJS package icon

Jering.Javascript.NodeJS

Jering.Javascript.NodeJS enables you to invoke javascript in NodeJS, from C#. With this ability, you can use NodeJS javascript libraries and scripts from C# projects.

Total Downloads
6.6M
6,614,157
Published
Jul 28, 2023
Latest stable version

Install

.NET CLI
dotnet add package Jering.Javascript.NodeJS --version 7.0.0-beta.5
Package Manager Console
Install-Package Jering.Javascript.NodeJS -Version 7.0.0-beta.5
PackageReference
<PackageReference Include="Jering.Javascript.NodeJS" Version="7.0.0-beta.5" />

Frameworks

.NETFramework4.6.1 .NETCoreApp3.1 net5.0 net6.0 net7.0 .NETStandard2.0

Dependencies

[2.2.0, )
[6.0.0, )
Microsoft.Extensions.Http
.NETFramework4.6.1
[6.0.0, )
[6.0.0, )
[6.0.0, )
System.Text.Encodings.Web
.NETFramework4.6.1
[6.0.0, )
System.Text.Json
.NETFramework4.6.1
[6.0.5, )
[6.0.0, )
[6.0.0, )
[6.0.0, )
[6.0.0, )
System.Text.Json
.NETCoreApp3.1
[6.0.5, )
[6.0.5, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.

The published metadata declares 42 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.