npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

browser-csharp

v1.1.2

Published

Executes C# snippets in the browser.

Readme

Browser C#

Executes C# snippets in the browser.

Installation

Install using npm:

npm install browser-csharp

The WASM files for .NET must be included as static assets in the correct way:

  1. The folder ./node_modules/browser-csharp/out/_framework must be included as ./_framework relative to the <base/> of your HTML file.
  2. You must include a reference to the WASM .NET entry file:
    <script src="_framework/blazor.webassembly.js"></script>

After doing this you can include the client library in JS/TS with a regular require/import.

Usage

Include a reference to the library:

const BrowserCSharp = require("browser-csharp").BrowserCSharp; // JS
import { BrowserCSharp } from "browser-csharp";                // TS

Wait for the WASM library to initiate:

BrowserCSharp.OnReady(success => { /* Callback */ });

Run a code snippet:

BrowserCSharp.ExecuteScript(`Console.WriteLine("Hello from C#");`)
.then(response => {
	response.stdErr // String with errors (parsing and compilation)
	response.stdOut // String with C# output (runtime)
	response.result // The return value of the the expression
});

With an extra argument (a string) the code snippet can be run in the context of previous code snippets, that was run with the same context id.
This is good for creating REPLs.

BrowserCSharp.ExecuteScript(codeSnippet, contextId)

The return is the same, a Promise that resolves with an object of the same shape.

Example

For an example of what this package can do, look in the ./example folder for the code and here for a live demo.

Development

This package requires that .NET Core is installed for development. Download the SDK here.

To test the wasm part during development run dotnet run in the wasm directory to start a dev server. It will only include the wasm part, so use the following snippet to invoke the code.

DotNet.invokeMethodAsync(
	"BrowserCSharp", "ExecuteScript",
	`String.Concat("apa".Select(c=>(char)(c+1)))`
).then(console.log)

There's not much to test with the TypeScript part, but you can build it alone with npx gulp ts-build.

Building everything at once can be done with npx gulp ts-build wasm-build, or npm run prepack 🤷‍♀️.