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

@endo/common

v1.2.2

Published

common low level utilities

Downloads

8,562

Readme

@endo/common

A collection of common low level utilities.

Each of the utilities in this packages

  • are low level in the sense of not depending on anything higher level than ses, @endo/eventual-send, and @endo/promise-kit. Many depend on nothing beyond plain old JavaScript.
  • highly reusable, i.e., potentially useful many places.
  • sufficiently general that it would be awkward to import from a more specialized package.
  • can be explained and motivated without much external knowledge.

Each utility is in its own top-level source file, named after the main export of that utility. (This is often that file's only export.) The package.json also lists each as a distinct "export":. There is no index.js file that rolls them together. Thus, each importer must do a deep import of exactly the export it needs. Some implementations (bundlers, packagers) can thus do tree-shaking, omitted code that isn't reachable by imports.

Currently there are no src/something.js files. The only source files that would go in src/ are those that do not represent separately exported utilities.

Generally each utility also has its own test file. (An exception is that make-iterator.js is indirectly but adequately tested by test-make-array-iterator.js).

See the doc-comments within the source file of each utility for documentation of that utility. Sometimes the associated test files also serve as informative examples.