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 🙏

© 2026 – Pkg Stats / Ryan Hefner

astro-relatinator

v2.1.0

Published

Find related content in your Astro website or app

Readme

Astro Integration for Relatinator

An Astro integration for the humble library for finding related posts and content.

Installation

Assuming you're running Astro v3 or later, you can install this integration by running:

npx astro add astro-relatinator

OR

npm install astro-relatinator

Configuration

The integration takes four input arguments, paths, schema, similarityMethod, and debug.

  • paths is an array of paths to the .md or .mdx files you want to use for training the model. If you're using the Content Collections API, you can find these at ./src/collections/<collection-name>/.
  • schema is an array of frontmatter fields you want to use for training the model.
  • similarityMethod is the algorithm to use for training the model. Can be "tfidf" or "bm25".
  • debug is a boolean flag to enable debug mode. It gets VERY verbose, so use it with caution.

Example:

export default defineConfig({
  // ...
  integrations: [
    // ...
    relatinatorIntegration({
      paths: ["./src/content/posts"], // path yo your content files
      schema: ["title", "descriptions", "tags"], // frontmatter fields to use for training
      similarityMethod: "bm25", // use BM25 for training
      debug: true, // enable debug mode
    }),
    // ...
  ],
});

Note: the fields you specify in the schema array must be present in the frontmatter of the files you're training on. If they're not, the integration will throw an error or lead to unexpected results.

Usage

The integration hooks into the Astro build (or dev) process, and will train the model based on the files you've provided. You can then use the utility functions exported by the package (BM25Utils or TfIdfUtils, depending on your chosen similarityMethod) to find related content and terms.

Example:

---
import { getCollection } from "astro:content";
// Import the utils corresponding to your configured similarityMethod
// (BM25Utils in this example, matching the config example above)
import { BM25Utils } from "astro-relatinator";

const blogEntries = await getCollection("posts"); // assuming your collection is called posts
// let's say we want to compare against the first blog entry
const first = blogEntries[0];

// Concatenate the same fields we used for training and declare how many related posts we want to find
const related = await BM25Utils.findRelated(`${first.data.title} ${first.data.description} ${first.data.tags.join(' ')} ${first.body}`, first.id, 3)

---

<div>
<!-- render your related posts here -->
{ related.map((id) => {
  const post = blogEntries.find((post) => post.id === id);
  if (!post) return null; // Handle case where post might not be found
  return (
    <a href={`/posts/${post.slug}/`}> {/* Adjust href based on your routing */}
      <h2>{post.data.title}</h2>
      <p>{post.data.description}</p>
    </a>
  );
}) }
</div>

Note: The BM25Utils and TfIdfUtils objects also provide getTopTermsForId and getTopRelatedDocumentsForTerm functions, similar to the core relatinator library.

Development Server: When running astro dev, the integration uses debouncing (a small delay) before re-training the model after a markdown file change. This improves performance for larger sites by preventing rapid, successive re-trains during saves.