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 🙏

© 2025 – Pkg Stats / Ryan Hefner

xixth

v0.12.5

Published

package starter installation helper

Readme

xixthjs

  • are a helper for:
    • starter project repository through npm;
    • bin script registration(to package.json);

note

  • the example are made using npm and npx, you can also use other packge manager, however you need to stick with single package manager due to binary installation are mainly binded to packager manger you use to install the package;
    • impliying you can also uses bun and bunx and other equivalent;

installation

  • on terminal
npm i xixth

register binary script to your package

  • on terminal:
npx xixth-add-bin -n your-script-name -f script-file-name-with-ext.mjs
  • both -n and -f flags and its value are mandatory;

  • best practice of naming your-script-name is to add your package-name to avoid global script name collision;

  • edit your newly created script file;

uses

  • you can run this binary whether its:

    • installed through npm;
    • symlinked using link package manager api;
  • which then you can calls it using:

npx your-script-name