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

@ngirl/nom-search

v0.2.9

Published

Search query component with autocomplete

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

i8degreesi8degrees

Keywords

nomngirlsearchautocomplete

Readme

@ngirl/nom-search

A web component for providing search results capabilities via text input. Abstract data source back-ends can be used for modifying the query response result -- anything from a remote database to a locally cached JSON string can be used as a model.

NOTE(jeff): This module is still in its infancy. Most features are not yet implemented.

Features

  • OpenSearch spec

Reference Documents

  1. Google: Refine web searches
  2. MongoDB: Free-Text Search
  3. http://www.opensearch.org/Specifications/OpenSearch/1.1
  1. http://ceos.org/document_management/Working_Groups/WGISS/Interest_Groups/OpenSearch/CEOS-OPENSEARCH-BP-V1.1-Final.pdf
  2. https://eoxc.github.io/opensearch/
  3. https://codepen.io/fielding/pen/Vbdppm

Reference Query Results Response

https://en.wikipedia.org/w/api.php?origin=*&action=opensearch&format=json&search=anita

https://naughty.localdev/search/suggestion/?q=anita&format=json&output=firefox

  1. OpenSearch Query Response data and headers

  2. https://naughty.localdev/opensearch.xml

  • Top-right header of site has search icon that transitions to a pull down search dialog, much like Fielding's design

2017-12-09_avn.com-search-pulldown.png

See also

  • ./design/code/gsearch

    • This directory contains interesting snippet examples I stashed away of Google's Search widget as I was casually browsing the source tree of Google's Android API documentation.

    • design/code/docs.js

      • Absorb as much of this gem as possible; I have yet to see anything in there that is not directly applicable for us.
      • The URL cleanup methods for consistent serialization and de-serialization of search and query data inside a HTTP GET request ought to be 120% answered after we consume and implement these inside nom-search and ./routes/search.js. Yay!
      • These two methods ought to get us well upon our way: buildResourceList and parseResourceQuery.

Projects Using nom-search