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

cc-sharing

v1.0.12

Published

communication between sharinator iframes ...

Readme

cc-sharing client library

To be used by clients of the CC Sharintor

This library defines iFramePhone message signatures for the purpose of 'sharing' work between students and teachers.

Details

There are four message types defined:

  1. SharinatorInit
    • Sends data about the session in sharing-init format
  2. SharinitorInitResponse
    • Sends data about the session in sharing-init format
  3. SharinatorPublish
    • User intiated request for new data.
  4. SharinatorPublishResponse
    • Contents of publishable data in Publishable format.

To Build:

  1. Install dependencies: yarn
  2. Compile npm run build

Using this library

All of this subject to change out of the blue. As of 2017-09-06 the easiest / best thing to do is something like this:

    const context:Context = {
        protocolVersion: "1.0.0",
        user: 1, // <string>|<number>
        id: uuid.v1(),
        group: 2, // <string>|<number>
        offering: 3, // <string>|<number>
        class: 4, // <string>|<number>
        requestTime: new Date().toISOString()
    };

    const app:SharableApp = {
        // Describe the application:
        application: {
            launchUrl: "http://127.0.0.1:8080/src/demo/iframe.html",
            name: "demo iframe app"
        },

        getDataFunc: (context) => {
            // 1. Construct a unique url from the sharing context:
            const dataUrl = `${context.group.id}-${context.offering.id}-${context.user.id}`;
            // 2. The promise constructs a list of data Represnetations:
            return new Promise((resolve, reject) => {
                resolve([
                {
                    type: Text,
                    dataUrl: `this is the iframe response at ${new Date()}`
                }
                ]);
            });
        }
    };

    // Pass in an existing phone as first arg if you want to reuse it.
    sharing = new SharingRelay({app:app});
    const receivePub = (snapshot:PublishResponse) => console.log(snapshot);
    sharing.addPublicationListener({newPublication: receivePub});
    sharing.initializeAsTop(context);

Running the demo & tester app

You can view an online demo.

You can epxierment with that demo by cloning the gihub repo cc-sharing-demo

See that README document for more info.

Rough Messaging Diagram

messaging diagram