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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sdk-javascript-bridge

v2025.7.8

Published

Node.js wrapper for SdkJavascriptBridge Blazor WebAssembly

Readme

Sage Connector Integration Guide

This guide explains how to install and use the sdk-javascript-bridge Node module in this Vite + React + Blazor WebAssembly bridge solution.


1. Install the sdk-javascript-bridge Node Module

If you have the .tgz package (for example, sdk-javascript-bridge-1.0.0.tgz), run:

npm install ./sdk-javascript-bridge

Or, if the package is in another directory:

npm install /path/to/sdk-javascript-bridge-1.0.0.tgz


2. Blazor Runtime Availability

The Blazor WebAssembly runtime and related files are inside the sdk-javascript-bridge package under:

These files must be available to the browser at /public/_framework/.

This solution includes a script (copy-sage-framework.cjs) and a Vite plugin that automatically copies these files to public/_framework before both dev and build.
You do not need to run the script manually.
It is triggered automatically by Vite.


3. Reference the Blazor Runtime in HTML

Your index.html must include:

This is required for the bridge to work.


4. Start the Dev Server

Run:

npm run dev

or

vite

The Blazor runtime will be available, and the bridge will work.


5. Usage

  • The UI provides buttons to call static methods and test advanced method calls.
  • The bridge logic is in bridge-tools.js.
  • Debug output appears in the "Debug Information" panel.

6. Troubleshooting

  • If you update or reinstall sdk-javascript-bridge, restart the dev server to ensure the latest files are copied.
  • If you move the copy script, update the path in vite.config.js.
  • If you see errors about missing _framework files, ensure the install and copy steps above are complete.

7. Project Structure

  • copy-sage-framework.cjs — Copies Blazor files from the node module to public/_framework.
  • vite.config.js — Runs the copy script automatically.
  • bridge-tools.js — Main bridge logic for interacting with Blazor.
  • index.html — Loads the Blazor runtime and bridge scripts.

You are ready to use the Sage Connector in your Vite + React project!