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

react-conf-webrtc

v0.0.31

Published

WebRTC conference room component for React projects. Out of the box support for Spreed WebRTC.

Downloads

208

Readme

react-conf-webrtc · CircleCI npm version

WebRTC conference room component for React projects. Out of the box support for Spreed WebRTC.

Demo

https://teamious.github.io/react-conf-webrtc/

Development

To start developing, first make sure you have installed all of the dependencies:

npm install

Next, you should link your local package. This lets you develop + test your packages locally. To link react-conf-webrtc first CD into the main project directory.

$ cd /path/to/react-conf-webrtc

Then run:

# You might need sudo
npm link

After that, change into the docs directory:

cd docs

and link the package:

npm link react-conf-webrtc

You will need to run a build in order to test with npm link:

cd  ~/react-conf-webrtc
npm run build:watch

You can develop in one of two ways: with docker or without docker. The recommended dev environment is to use Docker on your machine. You can still develop even if you can't run Docker on your machine.

With Docker

With Docker installed on your machine you can start the dev environment with the following command:

npm start

NOTE: This script assumes you are able to run docker with non-root access (you don't need to use sudo docker ...). You can learn how to do that here https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo

This does the following:

  • start webpack-dev-server
  • pull the spreed/webrtc image from Docker registry
  • run the spreed/webrtc image in a container

Please note that the boot time for the server can be a little slow. Once you see the following line you can know the server is up and running:

[1] server 2017/08/03 21:52:08 Starting HTTPS server on 0.0.0.0:8443

If you want to kill the dev environment simply press CTRL+C. This will kill webpack-dev-server and will also stop the docker container. NOTE: Stopping the previous docker container can be slow.

Without Docker

Without Docker installed on your machine you can still develop in your local environment. You will need to go to the Spreed Github page and clone the repository.

Once you have cloned the repository, look at the README.md file to learn how to start the Spreed server. Once you have the Spreed server up and running you can start webpack-dev-server with:

npm run start:no-docker

This system requires that you manually start and stop your spreed server.

Servers

Regardless if you start with/without Docker, your frontend server is available on https://localhost:8080 and your backend Spreed server is available on https://localhost:8443. Since both servers use self-signed certificates you will need to manually accept the warnings for both servers when testing in browser.

Both servers listen on 0.0.0.0, therefore you can connect to the servers on your network by knowing your host's IP address (eg. navigating to https://192.168.220.116:8080 you will find Andrew's dev server). This lets you test your server with multiple machines on the same network.