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

@vega-ui/react

v2.4.0

Published

Vega UI Kit for React

Readme

@vega-ui/react

React component library for VegaUI.

Requirements

  • react ^19.0.0
  • react-dom ^19.0.0
  • a bundler that can import package CSS

Installation

Install the component package together with the global theme package:

pnpm add @vega-ui/react @vega-ui/theme-core

Why both:

  • @vega-ui/react provides components and compiled component CSS
  • @vega-ui/theme-core provides the semantic theme variables those components rely on

Styles

Import the theme and component stylesheet once near the application entrypoint:

import '@vega-ui/theme-core';
import '@vega-ui/react/style.css';

If your app uses CSS layers, keep VegaUI below app-specific overrides:

@import url('@/shared/styles/normalize.css') layer(reset);
@import url('@vega-ui/theme-core') layer(theme);
@import url('@vega-ui/react/style.css') layer(library);

@layer reset, theme, library, app, overrides;

Quick Start

Apply a theme class at the app boundary, then render components normally:

import '@vega-ui/theme-core';
import '@vega-ui/react/style.css';
import { Button } from '@vega-ui/react';

export function App() {
  return (
    <div className='light'>
      <Button>Save changes</Button>
    </div>
  );
}

Built-in theme classes are .light and .dark.

Common Import Paths

import { Button, Dialog, Select, TextField } from '@vega-ui/react';
import type { ButtonProps, SelectProps } from '@vega-ui/react';

The package also exposes per-component entrypoints:

import { Button } from '@vega-ui/react/Button';

Local Development

From the repository root:

pnpm install
pnpm storybook
pnpm --filter @vega-ui/react test
pnpm docs:validate

Package-local scripts:

pnpm --filter @vega-ui/react build
pnpm --filter @vega-ui/react test
pnpm --filter @vega-ui/react check-types

Documentation

Common Mistakes

  • importing @vega-ui/react/style.css without @vega-ui/theme-core
  • applying .light or .dark too deep in the tree instead of around the app shell
  • using raw palette tokens in app overrides instead of semantic theme variables
  • assuming the component package is fully themed without an app-level theme class