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

@aleksandr.ilinykh.weasl/interview-ui

v1.1.0

Published

Internal UI components for the interview task

Downloads

306

Readme

interview-ui

Internal UI component library used by the interview client. Published to npm as @aleksandr.ilinykh.weasl/interview-ui.

Scripts

npm install
npm test
npm run build

Releases

Versions follow semantic versioning. The version in package.json is the source of truth. Bump it in the pull request together with a CHANGELOG.md entry.

  • Prerelease. Every push to a branch other than main publishes <version>-<branch>.<run> under the npm tag next. The exact version is printed in the workflow summary. Install it in a client with npm install @aleksandr.ilinykh.weasl/interview-ui@<that version>.
  • Release. Every push to main publishes the version from package.json under the latest tag, tags the commit v<version> and creates a GitHub release. If that version is already on npm the workflow does nothing, so merging without a version bump is safe.

Both workflows need the repository secret NPM_TOKEN with publish rights for the package.