Question 1

How do I call a .NET function from Node.js using Edge.js?

Accepted Answer

Define a .NET method with the signature `async Task<object> Invoke(object input)` in inline C# or a pre-compiled assembly, then use `edge.func()` to create a JavaScript proxy. The README provides examples with both callback and promise patterns.

Question 2

Edge.js vs using child processes or IPC for .NET and Node.js communication

Accepted Answer

Edge.js offers lower latency by running in-process, avoiding serialization and IPC overhead. However, it ties you to .NET runtime dependencies and can be more complex to debug compared to separate processes, which offer better isolation.

Question 3

How to debug Edge.js applications with .NET code?

Accepted Answer

On Windows, attach a managed debugger like Visual Studio to node.exe and set breakpoints. For embedded C# code, set the EDGE_CS_DEBUG environment variable to generate debugging symbols, as noted in the debugging section.

Question 4

Setting up Edge.js on Ubuntu Linux with .NET Core

Accepted Answer

Install .NET Core SDK, then run `npm install edge-js`. The library compiles binaries during installation using node-gyp. Set EDGE_USE_CORECLR=1 to ensure it uses .NET Core instead of Mono.

Question 5

Can Edge.js work with the latest .NET versions like .NET 9?

Accepted Answer

Yes, the README confirms support for .NET Core 3.1 through 9.x on Windows, Linux, and macOS. You need to set the EDGE_USE_CORECLR environment variable and ensure proper runtime dependencies are installed.

Question 6

How to handle exceptions when calling .NET from Node.js in Edge.js?

Accepted Answer

Exceptions are marshaled automatically: .NET exceptions become JavaScript errors in the callback with detailed stack traces, and JavaScript errors thrown in Node.js functions called from .NET are wrapped in CLR exceptions.

Question 7

Packaging Edge.js with Webpack or Next.js for production

Accepted Answer

The README specifies configuring edge-js as an external module in Webpack or using serverExternalPackages in Next.js to avoid bundling issues, since Edge.js relies on native binaries and .NET assemblies.

Edge.js

What is Edge.js?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions