Skip to main content
Echo.ProcessJS package icon

Echo.ProcessJS

Javascript actor library that works with LanguageExt.Core and Echo.Process: A library that uses and abuses the features of C# 6 to provide a functional 'Base class library', that, if you squint, can look like extensions to the language itself. It also includes an 'Erlang like' process system (actors) that can optionally persist messages and state to Redis (note you can use it without Redis for in-app messaging). The process system additionally supports Rx streams of messages and state allowing for a complete system of reactive events and message dispatch.

Total Downloads
87.1K
87,138
Published
Jul 28, 2022
Latest stable version

Install

.NET CLI
dotnet add package Echo.ProcessJS --version 2.1.35-beta
Package Manager Console
Install-Package Echo.ProcessJS -Version 2.1.35-beta
PackageReference
<PackageReference Include="Echo.ProcessJS" Version="2.1.35-beta" />

Frameworks

.NETFramework4.6.1 .NETStandard2.0

Dependencies

Echo.Process
.NETFramework4.6.1
[2.1.35-beta, )
LanguageExt.Core
.NETFramework4.6.1
[4.2.9, )
LanguageExt.Parsec
.NETFramework4.6.1
[4.2.9, )
Echo.Process
.NETStandard2.0
[2.1.35-beta, )
LanguageExt.Core
.NETStandard2.0
[4.2.9, )
LanguageExt.Parsec
.NETStandard2.0
[4.2.9, )

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

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 2 target frameworks; confirm the exact target used by your application.

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.