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

flumeview-vector

v2.0.0

Published

A very light weight and flexible index that allows rich queries.

Downloads

2

Readme

flumeview-vector

A very light weight and flexible index that allows rich queries.

Internally, the index is like an array inside a hash table: {<key>:[offset,...],...}

Think of each array as a subset (a filtering) of the flumelog. It's in the same order as the main log, but only contains records that have some specific property (represented by the key). Since each array is in the same order, it's very fast to do intersections on them, which allows logic operations like AND/OR on multiple properties at once without needing to create compound indexes. This means a small amount of indexes can support a large amount of queries. Also, indexes are sufficiently small that they can just be generated when needed.

Flumeview-Vector must be used with a flumeview-log that uses bipf format.

api

FlumeViewVector = require('flumeview-vector')

FlumeViewVector() => fvv

fvv.query({query, reverse, limit})

query is a possibly nested tree of expressions [OP, subexpression...|args...] OP be 'AND' 'OR' 'DIFF' or 'EQ'

  • 'EQ' expressions are of the form ['EQ', [path...], value] (path is an array of strings, value is a primitive js value) EQ queries matches any record that has the requested value at the requested path.
  • 'AND' expressions take 2 or more sub expressions. the output will be records matched by all sub expressions.
  • 'OR' expressions take 2 or more sub expressions. the output of an OR query will be records matched by any sub expression. records appearing in more than one subexpression will occur only once in the output.
  • 'DIFF' takes only two sub expressions. The output will be records in the first but not in the second.

the order of subexpressions in AND and OR expressions do not matter, but the order does matter for DIFF.

License

MIT