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

web-streams

v0.8.0

Published

Reference implementation and tests for the WHATWG Streams Standard

Downloads

6

Readme

Reference Implementation and Tests

This folder contains a reference implementation of the streams standard, inside lib/. It also contains a test suite inside test/.

Reference Implementation

The reference implementation is meant to be a fairly close transcription of the spec into JavaScript. It is written in modern JavaScript and primarily tested in Node.js; at least version 6.0.0 is required.

Tests

Test coverage is not complete, but we do aim for it to be. Adding tests would be a great way to contribute to this project.

You can check the test coverage at any time by running npm run coverage in this folder.

Original Tests

The original tests are written using the tape framework.

  • To run them, type npm test in this folder.
  • To run a specific test file, type e.g. node test-runner test/readable-stream.js.
  • To run a specific test, change the source file's test(...) call to test.only(...), then run npm test.

Web Platform Tests

After we started implementing this in browsers, we realized that we should probably have written the tests in standard web platform tests format. Fixing this has been an ongoing effort, with major help from WebKit contributors, who ported the initial set of tests from our original format.

The web platform tests for streams are found in the streams directory of the web platform tests repository, and maintained via pull requests to that repository.

For local development while working on the spec, you can run

bash ./update-web-platform-tests.sh

to clone the web platform tests repository locally, and then use

npm run wpt

to run the streams web platform tests against the reference implementation, inside a Node.js emulated-DOM environment. If you make changes to the tests locally, for example while making a spec change, please send them as a pull request to the web platform tests repository.