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

piral-search

v1.5.4

Published

Plugin for centralizing search in Piral.

Downloads

1,651

Readme

Piral Logo

Piral Search · GitHub License npm version tested with jest Community Chat

This is a plugin that only has a peer dependency to piral-core. What piral-search brings to the table is a set of Pilet API extensions that can be used with piral or piral-core to bring enhanced search capabilities to pilets via your Piral instance.

By default, these API extensions are not integrated in piral, so you'd need to add them to your Piral instance.

Why and When

In many cases the frontend should provide an extensive search functionality. If this search can or should also work in context-sensitive ways (e.g., depending on which microfrontends are loaded different search options are used or available) then this plugin might be useful. It allows pilets to register search providers which can handle search queries.

Video

We also have a video for this plugin:

@youtube

Documentation

The following functions are brought to the Pilet API.

registerSearchProvider

Adds a search provider to be used in the app shell. The search provider will always be invoked when the global search is triggered.

If the first argument is a string a named search provider is registered. A named search provider can also be removed.

unregisterSearchProvider

Removes a search provider from the app shell. This requires a named search provider.

Usage

::: summary: For pilet authors

You can use the registerSearchProvider function from the Pilet API to add a new search provider in the app shell.

Note: When the first argument is a string we call it a named search provider.

Example use:

import { PiletApi } from '<name-of-piral-instance>';
import { MyTile } from './MyTile';

export function setup(piral: PiletApi) {
  piral.registerSearchProvider(MyTile);
}

You can use the unregisterSearchProvider function from the Pilet API to remove a previously added search provider from the app shell.

Note: You'll need to have added a named search provider in order to be able to remove it.

Example use:

import { PiletApi } from '<name-of-piral-instance>';
import { MyTile } from './MyTile';

export function setup(piral: PiletApi) {
  // register with a name
  piral.registerSearchProvider('first', MyTile);
  // and unregister; maybe some time later?
  piral.unregisterSearchProvider('first');
}

:::

::: summary: For Piral instance developers

The provided library only brings API extensions for pilets to a Piral instance.

For the setup of the library itself you'll need to import createSearchApi from the piral-search package.

import { createSearchApi } from 'piral-search';

The integration looks like:

const instance = createInstance({
  // important part
  plugins: [createSearchApi()],
  // ...
});

Via the options the initially displayed results can be defined. The current query can also be set.

For example:

const instance = createInstance({
  // important part
  plugins: [createSearchApi({
    query: '!help',
    results: [
      <div>
        Help was found!
      </div>,
    ],
  })],
  // ...
});

:::

License

Piral is released using the MIT license. For more information see the license file.