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

@databiosphere/findable-ui

v52.1.0

Published

- `src` contains TypeScript source files; `lib` will contain compiled JavaScript, which is what should be imported by the external application. - Import paths used by the external application need to specify the full path starting from the package name,

Vulnerabilities

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

Links

Git

Maintainers

eweitzeweitzdsp-devopsdsp-devopsnoopdognoopdogbvizzierbvizzier

Keywords

Readme

findable-ui

General info

  • src contains TypeScript source files; lib will contain compiled JavaScript, which is what should be imported by the external application.
  • Import paths used by the external application need to specify the full path starting from the package name, in the form @databiosphere/findable-ui/lib/<path>, where <path> is the path of the file within the lib folder.

Developing findable-ui alongside a consuming app

Use scripts/link.sh to build and install a local copy of findable-ui into a consuming project (e.g. ncpi-dataset-catalog, data-browser):

  1. Clone this repository into the same parent folder as the consuming app.

  2. Set node version to 22.12.0.

  3. Run npm install in both repositories.

  4. From the consuming project directory:

    ../findable-ui/scripts/link.sh

    This compiles TypeScript, packs the output, installs it into node_modules, clears the Next.js cache, and starts the dev server.

  5. To iterate: Ctrl+C the dev server, make changes in findable-ui, and hit up-arrow to re-run the script.

  6. To restore the published version:

    ../findable-ui/scripts/unlink.sh

Consuming projects can optionally add thin wrappers in their package.json scripts:

{
  "scripts": {
    "link-findable": "../findable-ui/scripts/link.sh",
    "unlink-findable": "../findable-ui/scripts/unlink.sh"
  }
}