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

search-algorithm-design

v1.0.2

Published

-- basic features Suggestions items that are related or similar search resiliancy small user errors shouldn't defer from getting the correct results autocomplete guess user intent based on current

Downloads

1

Readme

Search Algorithm Research

-- basic features

  • Suggestions

    • items that are related or similar
    • search resiliancy
      • small user errors shouldn't defer from getting the correct results
      • autocomplete
        • guess user intent based on current entry
  • Search Process

    • Ranking
      • One large switch we could control would be ranking. First it would be trivial to add weights to the search and tweak them in the future. These weights could be based on various factors

        • how close the users search is to item
        • how often we sell a product
        • how much margin do we have in a product
      • This information would need to be on a dedicated and contained backend since it would have margin information.

      • this backend would have to scale and would have to be able to handle our server load, which can include 1000 queries a day, with more many more possible for auto complete