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

@grafana/labels

v1.6.7

Published

Service Labels

Downloads

4,339

Readme

@grafana/labels

Getting Started

The following guide is for consuming the library imports

  1. Import core component
import { ServiceLabels } from '@grafana/labels'
  1. Render ServiceLabels
<ServiceLabels
  value={options}
  errors={{}}
  loadById
  onLoadKeys={() => Promise.resolve(keys)}
  onLoadValuesForKey={() => Promise.resolve(values)}
  onCreateKey={() => Promise.resolve(undefined)}
  onUpdateKey={() => Promise.resolve(undefined)}
  onCreateValue={() => Promise.resolve(undefined)}
  onUpdateValue={() => Promise.resolve(undefined)}
  onRowItemRemoval={() => {}}
  onDataUpdate={(result) => console.info(result)}
/>

Props you may want to pass to the component

  • valueField - (optional) Field name for the id field (defaults to id)
  • labelField - (optional) Field name for the value field (defaults to name)
  • loadById - (optional - defaults to true) If true this will pas the id to some callbacks that fetch that, otherwise it will pass the value
  • onLoadKeys - Callback for fetching the keys
  • onLoadValuesForKey - Callback for fetching the values for a key
  • onCreateKey - Callback for requesting data whenever a new key is added
  • onUpdateKey - Callback for requesting data whenever a key is updated (edited)
  • onCreateValue - Callback for requesting data whenever a new value is added
  • onUpdateValue - Callback for requesting data whenever a value is updated (edited)
  • onRowItemRemoval - (optional) Callback for when a row is being removed (clicked X)
  • onDataUpdate - Callback for whenever the data changes (add/edit/add new row/remove row)

valueField and labelField allow customizing the data type you pass to the component in case you don't want to follow id/name convention

The following guide is for running the development version

To bootstrap both the webpack server and the library build:

  1. Open terminal and run yarn watch in the frontend directory - this will watch for any changes in library
  2. Run yarn link to allow creating a symlink to this directory
  3. In your grafana plugin directory, run yarn add '@grafana/labels'

Available commands

yarn build // triggers webpack to build the library  
yarn watch // triggers webpack to watch for library changes  

NPM library publishing

  • Update version in package.json
  • Run npm publish, authenticate and voila!