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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@agoric/lib-cosmic-relayer

v0.3.1

Published

Bridge from Node.js to the Cosmos IBC relayer

Downloads

14

Readme

Node.js Clib Bridge

This package is a template for writing a Node.js addon that communicates via function calls into a multithreaded C library.

The example, compiled with make and run with ./runner.js shows how a Golang shared library can be used from Node.js without running into synchronization problems. Downcalls to Golang are synchronous (they return when the Golang thread returns), and upcalls are asynchronous (they are enqueued and dispatched to the Node.js event queue, returning to Golang only when the returner's .resolve or .reject callbacks are called).

The C API exposed by clib.go is an example of what you will probably need to do in your own projects. Note that "ports" are increasing integers for naming the endpoints in the runner and the clib, and to which pending upcall the resolve/reject is directed.

Adopting these conventions was driven by the mismatch between Golang (synchronous, multithreaded) and Node.js (asynchronous, event-driven), and it is probably useful for other languages that can compile into a C shared library. Not too useful outside of Node.js, though. Maybe later.

Have fun, Michael FIG [email protected], 2020-06-02