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

dino_ui_tools

v2.42.3

Published

UI library for Dino

Readme

Dino UI Tools

See UI library for live demos and comprehensive docs.

Installation and usage

npm install dino_ui_tools

Then use it in your app:

import React from 'react';
import { Button } from 'dino_ui_tools/components/Button';
import 'dino_ui_tools/assets/styles/styles.scss'; 
// Or you can import the styles.css file
// import 'dino_ui_tools/assets/styles/styles.css';

const App = () => {
  return <Button>Click me</Button>;
};

How to use mixins:

@use "dino_ui_tools/assets/styles/helpers/mixin";

.divider {
    @include mixin.flexbox();
}

How to create new icon

1. Add a new svg file in `svg-icons` folder.
2. Make sure the icon is matching with the design.
3. Make sure the svg file name is matching with pattern like this `chevron-right.svg`.
4. Run `npm run generate-svg-component` command to generate the new icon component.

How to create new component

1. Add a folder with the component name in `src/components/` folder.
2. Add a style file in the `assets/styles/components` fodler with the name `_componentName.scss`.
3. Import the created style file in `assets/styles/styles.scss` file using @use syntax.
4. Develop component based on the design.
5. Add `coomponentName.stories.tsx` file in src/stories folder to test created component.
6. Make sure you don't have type error and the component is matching with the design.
7. If everything is ok you can create a pull request into the master branch with correct commit message (you can read about it below).
8. The new version will be published automatically after the pull request is reviewed and merged.

Automated Releases with Semantic Release

This project uses Semantic Release to automate versioning and releases. It follows Semantic Versioning (semver) and determines the next version number based on commit messages.

How It Works

Semantic Release automates:

1. Version number updates.
2. Release notes generation.
3. Package publishing to npm.
4. GitHub release creation.

Commit Message Guidelines

Semantic Release uses Conventional Commits to determine release types:

`fix:` – for bug fixes (patch release)
`feat:` – for new features (minor release)
`BREAKING CHANGE:` – for breaking changes (major release)

Releasing

To trigger a release:

1. Commit your changes using the conventional commit format.
2. Open a pull request and merge it into the `master` branch with the appropriate commit message.

Semantic Release will handle the rest, including publishing to npm and creating a GitHub release.