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

ssb-fixtures

v4.0.1

Published

Generate a simulated .ssb folder

Downloads

236

Readme

ssb-fixtures

A generator of fake ("Lorem ipsum") .ssb databases.

npx ssb-fixtures --messages=1000 --authors=100

Usage

ssb-fixtures [opts]

Options:
  --help            Show help                                          [boolean]
  --version         Show version number                                [boolean]
  --seed            String for deterministic generation
  --messages        Num of msgs to generate                     [default: 10000]
  --authors         Num of feeds to generate                      [default: 150]
  --outputDir       Directory for the output fixture           [default: ./data]
  --slim            Keep only essential flume files    [boolean] [default: true]
  --allkeys         Output all secret key files       [boolean] [default: false]
  --followGraph     Output follow-graph.json too      [boolean] [default: false]
  --indexFeeds      Percentage (0–100) of authors to write index feeds
                                                                    [default: 0]
  --indexFeedTypes  Comma-separated msg types for indexes
                                                      [default: "about,contact"]
  --report          Create a report.md file in the fixture       [default: true]
  --latestmsg       1-based index position of the LATESTMSG
  --progress        Print progress report to stdout   [boolean] [default: false]
  --verbose         Print all generated msgs to stdout          [default: false]

Features

  • Distribution of message types follows a real world distribution
  • Distribution of messages per author follows the Pareto distribution with α=2
  • Generates post msgs
  • Generates about msgs
  • Generates vote msgs
  • Generates contact msgs
  • Generates private post msgs
  • Oldest msg is always type: post and contains the text "OLDESTMSG"
  • Most recent msg is always type: post and contains the text "LATESTMSG"
  • Can generate an "extended" fixture
    • npx ssb-fixtures --seed=foo --messages=1050 --authors=100 --latestmsg=1000 contains 50 more new messages more than npx ssb-fixtures --seed=foo --messages=1000 --authors=100
  • Can generate meta feeds and index feeds

Versioning

This does not follow SemVer. That's because we want to version the datasets primarily, not the code that produces the dataset. This is how we update versions M.m.p:

  • M: updated when the dataset changes even when parameters seed, messages, authors remain the same
  • m: updated when the source code and CLI get breaking changes or new features, i.e. noticeable changes
  • p: update when the source code and CLI receive bug fixes

TODO

  • Support npm and npx (it installs multiple versions of mock-monotonic-timestamp, messing up the mutable counter)
  • Generate channel messages
  • Private threads (currently all private messages are "root")