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

@scbd/generics

v0.0.3

Published

Downloads

3

Readme

Generics v2

Completed Features (as discussed at meetings + in addition to some of my own ideas)

  • NPM package
  • History of changes out side of collection
  • Metas out side of collection
  • Validation that complies with security policies
  • all schemas and definitions loaded so definition only declared once.
  • Edge concept - all references to other documents will be in an edge schema
    • benefits for keeping track of dead references to deleted or archived records
    • establishing relationships of data
    • enable easy triggering of indexation of parents who may index some child info
  • EdgeFixed - references the history version of the document and never changes.
  • lString collection - all lStrings in one place for easier translations of data.
  • Data structure follows an object oriented inheritance structure. Inspired by schema.org founded by Google, Microsoft, Yahoo and Yandex. I argue that object orientation and inheritance is not maintainable. Further I argue functional programing is better. These arguments do not apply to data structures though! Google, Microsoft, Yahoo and Yandex.
  • url collection for external references, one collection for easy 404 checking.
  • separation of middleware by concerns (ability to overwrite each)
    • sanitize
    • security
    • Validation
    • meta
    • pre query
    • query
    • post query
    • afterware - to be called at the end of the express route "creating mq msgs"
  • localization
  • lstring schema keys
  • auto indexing of keys / specifying indexes in schema.
  • property alias's
  • title/name to ID
  • identifier is full url

In progress:

  • 60% finished edger, api automatically build an edge when pointing to another schema.
  • 40% tests - for new features

Todo: afterware - workingDocument - all documents not in their final or intended state will reside in working documents. edger - automatically build edge collection entry for our own registered schemas referenced.
returning children object in query option.