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

@extravirgin/payload-plugin-meilisearch

v0.0.16

Published

Index your payload collections to meilisearch

Readme

Payload Meilisearch plugin

Indexing fields from relationships

Relationship fields are indexed as IDs by default. To make selected values from the related documents searchable, configure indexRelationshipFields. The relationship ID is retained alongside the selected fields.

meilisearch({
  apiKey: process.env.MEILISEARCH_API_KEY,
  host: process.env.MEILISEARCH_HOST,
  collections: [
    {
      slug: 'posts',
      indexRelationshipFields: {
        category: ['name'],
        tags: ['name', 'slug'],
      },
    },
  ],
})

For example, a populated category relationship is indexed as:

{
  category: {
    id: 'category-id',
    name: 'Engineering',
  },
}

hasMany relationships produce an array of these objects. Polymorphic relationships also retain relationTo. Both the relationship field key and selected related field names support dot notation:

indexRelationshipFields: {
  'meta.category': ['name', 'seo.title'],
}

The option can be set globally and overridden per collection. When it is enabled, the plugin reads the source document at a depth of at least 1 so direct relationship values are populated. Changes to a related document do not by themselves run the source collection's hooks; reindex the source collection when those values change.

Indexing localized select labels

Select values remain unchanged and can still be used for filtering. To also make their option labels searchable, enable indexSelectLabels. The label is added to a sibling field with the _label suffix.

meilisearch({
  apiKey: process.env.MEILISEARCH_API_KEY,
  host: process.env.MEILISEARCH_HOST,
  collections: [{ slug: 'products' }],
  indexSelectLabels: true,
})

For a document locale such as en-US, labels are tried in this order: en-US, en, then Payload's i18n fallback language. The behavior can be configured globally or overridden per collection:

meilisearch({
  // ...
  collections: [
    {
      slug: 'products',
      indexSelectLabels: {
        defaultLocale: 'de',
        fieldSuffix: '_optionLabel',
        resolveLabel: ({ defaultLabel, option, localeFallbacks }) => {
          // Useful for function labels or application-specific translations.
          return defaultLabel
        },
      },
    },
  ],
})

Returning undefined from resolveLabel keeps the built-in result. Returning null omits the label.