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-protocol-expect

v1.0.0

Published

A function for expecting/awaiting matching data from a readable stream (for line-by-line request-response protocols)

Downloads

4

Readme

npm version npm downloads Build Status Unlicense

stream-protocol-expect

A tiny function for expecting matching data from a readable stream, e.g. for request-response protocols like SMTP and IMAP.

Usage

First argument: the stream.

Second argument: matcher function or a regexp. Make sure the stream is textual (an encoding is set), otherwise it will try to call your function or regexp .match on a Buffer! (Your function can handle Buffers if you want, but there's no match on them :D)

Third argument (optional, default = 4s): timeout (zeit/ms).

Returns: a Promise that will be resolved with the matching data or rejected with an error.

For example, IMAP authentication:

(async function () {
	const streamExpect = require('stream-protocol-expect')
	const tls = require('tls')
	const sock = tls.connect(993, 'mail.example.com')
	sock.setEncoding('utf-8')
	sock.setNoDelay(true)
	console.log('Got response: ', await streamExpect(sock, x => x.includes('OK')))
	sock.write('a login [email protected] hunter2\r\n')
	console.log('Got response: ', await streamExpect(sock, /^a\s*OK/, '1s'))
  // exception if not OK
	sock.end()
})()

Possibly something like byline might be helpful to ensure that it will actually match line-by-line.

Installation

Install with npm:

npm i stream-protocol-expect

Contributing

Please feel free to submit pull requests!

By participating in this project you agree to follow the Contributor Code of Conduct and to release your contributions under the Unlicense.

The list of contributors is available on GitHub.

License

This is free and unencumbered software released into the public domain.
For more information, please refer to the UNLICENSE file or unlicense.org.