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

@getgrover/ui

v6.12.0

Published

Reusable UI components for grover web apps

Vulnerabilities

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

Links

Git

Maintainers

getgrovergetgrover

Keywords

Readme

Grover UI react components

[!TIP] Are you looking for help migrating to v6? Check out the migration guide.

Installation:

yarn add @getgrover/ui

Usage:

Import fonts:

Every consumer of this library is expected to add the required fonts on its own. This can be done by adding the following snippet to the <head> of your applications html:

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
    href="https://fonts.googleapis.com/css2?family=Inter:wght@300;500;700;800&display=swap"
    rel="stylesheet"
/>

[!NOTE] Its also important that consumers set the font-family for the elements making use of the font. Starting in v6, theme.typography styles no longer set font-family for you. Recommended font-family: 'Inter', system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, 'Open Sans', 'Helvetica Neue', sans-serif;

Every component is a named export. You can import any component as follows:

import { Button } from '@getgrover/ui';

The UI library currently offers two different build outputs: umd (main) and esm (module). Depending on your build setup your bundler will prefer the tree-shakable esm.

Storybook

The storybook deployment for the UI library can be found here: https://main.ui-storybook-dev.eu-staging.grover.com/

Development:

This repository is maintained by @devsbb/retention but everyone is welcome to contribute. For contributing guidelines, please see contributing.

Local development process implemented through @storybook/react. Please read this documentation before staring developing new components.

  1. Create new component in /packages folder
  2. Import new component through init. file /index.ts
  3. Create new story in the component folder packages/NewComponent/NewComponent.stories.jsx
  4. Type yarn start to run the development server
  5. Storybook started on => http://localhost:6006/
  6. Repeat 1-4 ("Hot Module Replacement" is running)

Customization

We want consumers to be able to customize UI components according to their needs. Since we build all new components via styled-components, there are have two ways for a single component to allow it's customization:

  • if we want the consumer to slightly alter the component look, we export its settings via the theme.
  • if we want to allow any customization to build new components on top of the current one, we go with the classNames + styled.attrs approach (take a look at the Input component).

Release process

This project uses semantic releases.

[!IMPORTANT] PR names must follow Angular Commit Message Conventions. If they don't no release will be triggered, nor will the commit appear in the changelog part of the release.

[!IMPORTANT] When merging PRs, ensure that the "squash and merge" option is selected to ensure that each PR only results in a single changelog line. If the standard "merge" option is selected, each commit in the PR will appear as a separate changelog item.