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

@hacksc/ui-kit

v1.0.2

Published

The official HackSC UI kit

Vulnerabilities

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

Links

Maintainers

snokpoksnokpok

Keywords

Readme

HackSC official UI kit

We build everything here :)

Available Scripts

npm test

Launches the test runner in the interactive watch mode.

npm run build

Builds the UI kit for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.

Testing the UI kit in a demo app

If you want to test your changes for the UI kit on a separate React app, you will need to temporarily symlink the React dependency of your demo app to this package.

The reason is because we use React hooks in this UI kit :) and you would be running 2 instances of React per this when you do npm link @hacksc/ui-kit in your demo app if you don't do the below steps (or equivalent steps to ensure only one React instance is present on your demo app).

  1. cd to your demo app folder (should be a React/Next.js app)
  2. Make sure you installed all dependencies in your demo app via your favorite install command. This app must have a React dependencies version that is compatible with the React version specified in this package (in package.json's peerDependencies)
  3. cd back to our UI kit folder, and npm link ${PATH_TO_APP}/node_modules/react to temporarily symlink the demo app's React to this UI kit. the UI kit's
  4. Run npm link to create a global symlink for this UI kit
  5. cd back to the demo app
  6. Run npm link @hacksc/ui-kit to symlink the global symlink for the UI kit into the app's node_modules
  7. Start the demo app and start playing around with the kit! Since it's a symlink, any changes to the UI kit in the ui-kit/ folder will require a build first before it reflects on the demo app.