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

renderer-finder

v0.1.3

Published

DLNA renderer finder

Downloads

11

Readme

Renderer Finder

This module provides an event driven way of obtain all the DLNA renderers present in the network.

Usage

The module can be used to get the first renderer found or keep listening to new ones.

Getting only one

var RendererFinder = require('renderer-finder');
var finder = new RendererFinder();

finder.findOne(function(err, info, msg){
  console.log(info);
  console.log(msg);
});

The callback receive the info parameter with a basic data of the address of the renderer. The msg parameter contains the M-SEARCH parsed response data as a JSON.

Additionally you can ask for more data to the renderer. To do this you need to pass a true as the first parameter and the callback as a second parameter.

finder.findOne(true, function(err, info, msg, desc){
  console.log(info);
  console.log(msg);
  console.log(desc);
});

The desc parameter contains the data of the DLNA description asked to the renderer.

Event driven mode

The event driven mode have all the same capabilities of the 'get only one' mode but the finder keep looking for more renderers until you say stop.

To ask for more data, you need to pass true as the first parameter in the start method.

finder.on('found', function(info, msg, desc){
  console.log(info);
  console.log(msg);
  console.log(desc);
});

finder.start(true);

To stop searching you only need to call stop:

finder.stop();

Search for another devices

The constructor of the finder support a custom ST as the first parameter to search for custom devices.

The default ST is urn:schemas-upnp-org:device:MediaRenderer:1

var RendererFinder = require('renderer-finder');
var finder = new RendererFinder('urn:schemas-upnp-org:device:Basic:1');

finder.findOne(function(err, info, msg){
  console.log(info);
  console.log(msg);
});