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

@cirrobio/react-tool

v0.0.5

Published

React components and utilities for developing Cirro tools

Vulnerabilities

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

Links

Git

Maintainers

nth0rpenth0rpemzagercirrobiomzagercirrobio

Keywords

Readme

@cirrobio/react-tool

React Tool

React components and utilities for Cirro tools and viewers.

Exports

Providers

  • ViewerProvider

A context provider that wraps the tool in everything needed to interact with Cirro.

Hooks

  • useViewerState

    React hook to access the current state of the viewer. The viewer state is responsible for providing information to the viewer about the currently selected Cirro project, dataset, and files available.

  • useViewerServices

    React hook to access the services available in the viewer. The services can be used to interact with the Cirro API or files.

Developing Tools

Tools will need to use the ViewerProvider to wrap the tool's root component. This will provide the necessary context for the tool to function correctly.

The ViewerProvider takes the following props:

  • apiBasePath (optional)

    The base path for the Cirro API. If not provided, it defaults to /api. This will need to be changed in most cases unless you use vite-proxy or a similar proxy setup. This will be overridden by the viewer if it is in Embedded mode.

  • patchFetch (optional)

    If this is true, the fetch function will be patched to sign requests to S3 automatically if the prefix is provided (use getPatchedSignUrl). This is useful for tools where you do not have control over how it requests files. For example, some tools may only require you to input a base path to a file, and it uses HTTP Range requests or relative paths to access data (i.e., Zarr, OME-TIFF, etc.).

  • authProvider (optional)

    Use this to provide an authentication provider that will be used to authenticate requests to the Cirro API. This will default to AmplifyAuthProvider, but for local testing it may be useful to use StaticInteractiveAuthTokenProvider. If you have to override the OAuth client ID, please create a new instance of AmplifyAuthProvider with the desired client ID.

Examples

Image Viewer

Provides a basic viewer for png, jpeg, and svg images.

Local Development

The Cirro tool is designed to get the viewer state from the Cirro UI directly.

To test locally, you can add the projectId, datasetId, and file query params to the URL to fill out the project, dataset, and selectedFile in the viewer state, respectively.