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

@hypersign-dev/hypersign-ui

v0.8.34

Published

This project contains React components, icons, and typography for building applications across Hypersign.

Readme

Hypersign UI (Component Library)

This project contains React components, icons, and typography for building applications across Hypersign.

Development

Local usage

In order to import this package locally, you must first link it to the project you are working on. To link the project, first run the npm install command to make sure all dependencies are installed.

Register the package

In the directory for this package, run the following to register this package as a linkable package. npm link or yarn link

This will register the hypersign-ui package as a globally linkable package.

Link to your project

Now, move over to your target package. (i.e. whatever will be using hypersign-ui).

Link hypersign-ui to your target package by running: npm install ../path/to/your/package or yarn add link:../path/to/your/package

Handle import alias resolutions to your project

In order to properly import hypersign-ui into your project, you will need to tell vite where to look. We can do this by adding the following to the vite.config.ts file in the target project.

resolve: {
    preserveSymlinks: true,
    alias: {
      '@hypersign-dev/hypersign-ui': resolve(__dirname, '../../hypersign-ui/src')
    }
  },

Be sure to update the ../../hypersign-ui/src to the relevant path according to your individual file structure.

Storybook

We are currently using Storybook for development and testing of components.

  • Be sure to install dependencies with npm install
  • Run the Storybook server with npm run storybook
  • Running the Storybook server will also run npm run storybook:css, which overrides the index.css file with any used tailwind classes in the project. This is necessary for all styles to take effect.

Also, TailwindCSS is being used for all styling. Within Hypersign UI, all styling with Tailwind classes are prefixed with ui-:

<div className="ui-flex ui-flex-col ui-gap-1">...</div>

Deployment

We're working on it!

This is getting updated as we move the package from npm.js to AWS CodeArtifact.

Authentication

Open a terminal and run npm login

You will be prompted for you username, password, and email.

Validate your identity by running npm whoami

Deployment

Update the version number and run npm run build or yarn run build

Deploy the package to npm. Currently, the project is flagged as public, but that will be fixed in later versions.

npm publish --access public

The --access public argument is required because the package is a scoped package.

Validation

Navigate to npm.js

Search for @hypersign-dev/hypersign-ui

Validate that the version number you deployed is the latest version.