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

@etohq/search-legacy

v2.1.1

Published

Eto legacy search module — owns search provider registration and exposes the active provider

Readme

@etohq/search-legacy

eto's pre-port search contract, kept as it was so its users keep working while they move onto the new Search Module (@etohq/search, ported from Medusa). Nothing inside changed; only names, paths and the module key did.

New work should use @etohq/search. Don't add features here.

Renames

| Before | After | |---|---| | package @etohq/search | @etohq/search-legacy | | Modules.SEARCH ("search") | Modules.SEARCH_LEGACY ("search_legacy") | | AbstractSearchService | AbstractLegacySearchService | | SearchIndexGroup, SearchIndexDocument | LegacySearchIndexGroup, LegacySearchIndexDocument | | SearchQuery, SearchResult, SearchHit, SearchFacet | LegacySearchQuery, LegacySearchResult, LegacySearchHit, LegacySearchFacet | | SearchValue, SearchOperators, SearchCondition, SearchSort, SearchRanking | LegacySearchValue, LegacySearchOperators, LegacySearchCondition, LegacySearchSort, LegacySearchRanking | | SearchUtils (utils bundle) | SearchLegacyUtils | | ISearchService, IndexSettings (types) | ILegacySearchService, LegacyIndexSettings | | SearchTypes (types bundle) | SearchLegacyTypes | | @etohq/types/search, /search/interface, /search/settings | @etohq/types/search-legacy, /search-legacy/interface, /search-legacy/settings |

indexTypes, variantKeys and defaultSearchIndexingProductRelations keep their names. Modules.SEARCH now belongs to the new module.

The Trieve provider (@etohq/search-trieve) registers against Modules.SEARCH_LEGACY. Register both under the legacy key:

modules: {
  [Modules.SEARCH_LEGACY]: {
    resolve: "@etohq/search-legacy",
    options: {
      providers: [{ resolve: "@etohq/search-trieve", id: "trieve", options: { ... } }],
    },
  },
}