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

foglet-core

v5.1.2

Published

Core of the foglet library

Downloads

102

Readme

Foglet-core

Build Status npm version JavaScript Style Guide Documentation Status

NPM

Easy use of WebRTC Networks with embedded network management and simple communication primitives.

Read the documentation or read the API Documentation

Features

Communication primitives:

  • Broadcast (to all peers in your network, with an anti-entropy mechanism not enabled by default). We ensure single delivery and a causal relation between 2 consecutive messages from a same site.
  • Unicast (to one direct neighbor)
  • Multicast (to one or several direct neighbors)
  • Streaming over our Broadcast and Unicast
  • Multiple communication channel per network

We only support Data Channel for the moment.

  • Experimental Media Unicast and Broadcast

Warning: unicast media is working only for a period of time defined by the delta parameter in the RPS

Network management:

  • An adapter on ran3d/spray-wrtc as Random Peer Sampling Network (keeping log(NetworkSize) peers around you)
  • An adapter on Cyclon as Random Peer Sampling Network (keeping "maxPeers" peers around you)
  • Overlay Networks or Networks can be created with: ran3d/n2n-overlay-wrtc
  • Disable WebRTC for testing purposes (or simulation) by using our Simple-peer moc.

Installation

Prerequisite: a browser compatible with WebRTC

npm install --save foglet-core

The foglet library is distributed with its sources and a bundle for an in-browser usage.

Getting started

Creates a new HTML file and insert the foglet bundle in it:

<script src="node_modules/foglet-core/dist/foglet.bundle.js" type="text/javascript"></script> <!-- or use the minified bundle, foglet.bundle.min.js -->

Then, foglet library is available in the variable foglet :

const Foglet = foglet.Foglet;

If you do not provide a list of ice servers, your example will work in localhost but not on the Web.

To be begin with, let's write a simple piece of JS code:

<script type="text/javascript">
  'use strict';

  localStorage.debug = 'foglet-core:*';

  const Foglet = foglet.Foglet;

  // let's create a simple application that send message in broadcast
  const fog = new Foglet({
    id: 'myfogletid', // default we use uuid/v4 generated id
    rps: {
      type: 'spray-wrtc', // we choose Spray as a our RPS
      options: {
        protocol: 'my-awesome-broadcast-application', // the name of the protocol run by our app
        webrtc: { // some WebRTC options
          trickle: true, // enable trickle
          iceServers : [] // define iceServers here if you want to run this code outside localhost
        },
        signaling: { // configure the signaling server
          address: 'http://signaling.herokuapp.com', // put the URL of the signaling server here
          room: 'my-awesome-broadcast-application' // the name of the room for the peers of our application
        }
      }
    }
  });

  // connect the foglet to the signaling server
  fog.share();

  // Connect the foglet to our network
  fog.connection().then(() => {
    // listen for broadcast messages
    fog.onBroadcast((id, message) => {
      console.log('The peer', id, 'just sent me by broadcast:', message);
    });

    // send a message in broadcast
    fog.sendBroadcast('Hello World !');
  });
</script>

Then, open the HTML file and look into the developpers console. You should see that your foglet has been connected to the RPS.

Or for the fast version:

git clone https://github.com/RAN3D/foglet-core.git
cd foglet-core
npm install
npm run build
  • Open tests/examples/example.html in a browser supporting WebRTC and the devConsole

  • Try to play with testunicast() and testbroadcast()

or try the signaling example using a signaling server:

  • Just run a simple http server with an embedded signaling server serving the tests/examples/example-signaling.html: npm run example
  • open http://localhost:8000/signaling

Signaling server

In order to run this library, you have to provide the address of a signaling server using the signaling.address option and a signaling.room in order to create a private network. This server will be used to establish the first connection between the new peer and the the network.

This server must be compatible with the foglet library. The library foglet-signaling-server provides an example implementation of such signaling server.

Developpment

We offer another library which lets you to build/test/run your own application with a signaling server: https://github.com/ran3d/foglet-scripts.git

# Clone and install
git clone https://github.com/ran3d/foglet-core.git
npm install

# Build the bundle (webpack stack)
npm run build

# Lint using [standard](https://standardjs.com/)
npm run lint

# Mocha, chai stack with a simple-peer-moc for mocking webrtc features
npm run test

# Run a server serving examples and a signaling server on http://localhost:8000/
npm run example

Contributors: