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

stream-url

v0.2.3

Published

Stream URLs ===========

Downloads

13

Readme

Stream URLs

The package aims to unite two powerful universal concepts: streams and URLs. stream-url encapsulates details of a particular medium and allows the app to open data streams to URLs. stream-url is a syntactic sugar, in a sense, but it definitely helps to clear a subsystem's code out of technical details and make it easily pluggable.

    var su = require('stream-url');
    
    // TCP server
    var tcp_server = su.listen('tcp://localhost:1234', (err, serv) => {
        serv.on('connection', stream => {
        ...
        
    // stdin/stdout "client"
    su.connect('std:', (err, stream) => {
        ...

Build Status

API

  • listen(url [,options] [,callback]) start a server (stream factory) listening at the url, using options. Invoke callback(err, server) when ready or failed. The server will emit a connection event for every new incoming connection/stream.
  • connect(url [,options] [,callback]) connect to a server at (create a stream to) url. Invoke callback(err, stream) once ready to write or failed to connect. The stream will emit all the usual events: data, end, error.

This package defines just one fictive URL protocol named 0 which masquerades local invocations for a stream. The 0 protocol is mostly useful for connecting componenets locally. It is not that useful for unit testing as it skips serialization/ deserialization for the sake of efficiency. See test/ for usage examples.

All "real" protocols are defined in separate packages, as those introduce non-trivial dependencies.