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

victoria-react

v0.0.5

Published

Victoria design system built with React

Vulnerabilities

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

Links

Maintainers

unhandled_exceptionunhandled_exception

Keywords

design systemvictoriareact libraryreact

Readme

Development

This project primarily uses StorybookJS for development.

Quick Start

  1. git clone [email protected]:sikozonpc/victoria.git
  2. yarn
  3. yarn dev

Creating components

Make a new folder in the components folder, make sure the folder name is unspaced and Pascal Case (ExampleComponentName). Create a JS file with the same folder name (or appropriate variation).

Requirements

  • Documented PropTypes and default props.
  • Storybook examples are labeled with a .story.js filename.

Project Structure

The goal is to keep the package as lightweight and minimal as possible, so there's not much to it. If you look at the package.json, you'll see a few dev dependencies like Babel, React, and Storybook.

In terms of actual dependencies, we only have React-JSS, since it's used in the actual components. React and react-dom are peer-deps (since the project's using this will be react-based).

Folder Structure

  • lib/
    • /components/
    • /components/ComponentName/
    • /components/ComponentName/ComponentName.js
    • /components/ComponentName/ComponentName.stories.js - stories of the component
    • /components/ComponentName/ComponentName.test.js - unit tests
    • /components/ComponentName/index.js - contains exports of all components in folder
    • .babelrc - env and react Babel presets.

High Priority

  • More components

Low Priority

  • Integrate Jest + Storybook for testing

Thoughts

  • Install Lerna to manage sub-packages, allowing users to install specific components (maybe separate branch?)