Alethic.Node.Http 1.0.0

There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package Alethic.Node.Http --version 1.0.0
                    
NuGet\Install-Package Alethic.Node.Http -Version 1.0.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="Alethic.Node.Http" Version="1.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Alethic.Node.Http" Version="1.0.0" />
                    
Directory.Packages.props
<PackageReference Include="Alethic.Node.Http" />
                    
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 Alethic.Node.Http --version 1.0.0
                    
#r "nuget: Alethic.Node.Http, 1.0.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 Alethic.Node.Http@1.0.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=Alethic.Node.Http&version=1.0.0
                    
Install as a Cake Addin
#tool nuget:?package=Alethic.Node.Http&version=1.0.0
                    
Install as a Cake Tool

Alethic.Node.Http

Serving a JavaScript application over HTTP from Node embedded in a .NET process, whatever the .NET host. It holds the protocol the hosts share, so an application written for one is served unchanged by the other:

  • Alethic.Node.AspNetCore serves it from ASP.NET Core endpoints;
  • Alethic.Node.AspNet serves it from System.Web routes on .NET Framework.

An application is a self-contained CommonJS bundle whose default export has a fetch function, or is the function itself:

export default {
    fetch(request, env, ctx) { /* return a Response, or a promise of one */ },
};

FetchProtocol is how a host puts a request to it and reads its answer:

  • The request is the runtime's own Request. Its URL is the path below where the host mounted the application, under BaseUri, which is http://node.invalid/ unless set: not where the caller was. The host drops Host and writes X-Forwarded-Proto, X-Forwarded-Host and, below the root, X-Forwarded-Prefix itself, so they say where the caller was and a caller cannot say otherwise.
  • env holds the host's strings, from Environment, in an object made for each request.
  • ctx has waitUntil(promise), which only keeps a rejection from going unobserved, since a pooled engine keeps running, and passThroughOnException(), which does nothing.
  • The response's status, headers and body are the host's to write, less Content-Length and Transfer-Encoding, which the server frames itself.

FetchProtocolOptions holds what every host is configured with: BaseUri, Environment, and ResponseBody, a BodyMode:

  • Streamed: each chunk reaches the client as the application produces it. A failure after the first can only truncate the response.
  • Buffered: nothing is written until the application is done, so a failure is still one the host answers.

Each host's options extend it with what is its own.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Framework net472 is compatible.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Alethic.Node.Http:

Package Downloads
Alethic.Node.AspNetCore

Server-side rendering for ASP.NET Core on a Node runtime embedded in the process, over Alethic.Node's pooled engines: the rendering engine over the application's fetch export, and endpoint mapping driven by the application's own route manifest.

Alethic.Node.AspNet

Node embedded in an ASP.NET (System.Web) application on .NET Framework, over Alethic.Node's pooled engines: the application's pool, Node work done on behalf of a request with the request's own thread serving what it asks of the page, fetch answered in process by the site's own handlers, and whole pages from a JavaScript application's fetch handler, mounted on ASP.NET routes.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.1-pre.27 66 10/4/2026
1.0.1-pre.25 67 10/4/2026
1.0.0 233 10/3/2026
1.0.0-pre.37 81 10/3/2026