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

talloc

v1.0.3

Published

```bash git clone $REPO_URL $PROJECT_DIR cd $PROJECT_DIR yarn install yarn test ```

Downloads

3

Readme

Install

git clone $REPO_URL $PROJECT_DIR
cd $PROJECT_DIR
yarn install
yarn test

Vision

Goal: maximize production Goal (precise): maximize count of new objects over time period under the following conditions: objects must pass validation, time period is static Transformation: Input: world state + available transformations Output: messages for actors

  • Different starting parameters of each actor
  • Changing environment

Architecture

  • Should we use Errors to create tasks? (?) = But we won't be able to pull multiple tasks for different actors = But do we need that?
  • Functions or Functors? (Functors) = Functors support context = Functions can accept context as last argument = Functions can accept context via .apply() = Functors support multiple calls = Functors support states (may be necessary, may be not) = Functors support "blueprinting" via inheritance (e.g. SendAirdropMessage extends SendMessage) = Functors support simple helper calls via inheritance (no need to import them)
  • What to return from materializers? (null + run manually) ~ Blueprints = But may not be able to return full objects due to validation = But will have to generate tasks in parent functor ~ Tasks or Objects ~ null + execute tasks manually = And may be better flow control = And explicit