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

@rulecms/client

v0.3.0

Published

RuleCMS client library for pulling content from RuleCMS backend.

Downloads

43

Readme

RuleCMS Client Library

This project is generated by create-ts-fast, a tool for scaffolding npm libraries written in TypeScript.

Directory walkthrough

The project has the following files and directories:

├── .github/workflows/ci.yml
├── dist
├── src
│   ├── __tests__
│   └── index.ts
├── package.json
├── README.md
├── tsconfig.json
├── tsup.config.ts
└── vitest.config.ts
  • src: Contains source code
    • __tests__: Directory containing tests. Code within __tests__ will be ignored during build
    • index.ts: Main file
  • package.json: Self explanatory
  • README.md: Project's README file. Contents will be displayed on the package homepage on npmjs.com and repo homepage of github.com
  • tsconfig.json: Base TypeScript config. Used when developing
  • tsup.config.json: tsup config. Refer to its documentation for customization
  • vitest.config.ts: Vitest config. Refer to its documentation for customization
  • dist: Directory containing generated files. The contents of this directory is published
  • .github/workflows/ci.yml: GitHub action that runs typechecks, tests and build

Next steps

  1. Implement your library within src. Add tests if you take pride in being a developer
  2. Modify package.json – update name, version, author and any other relevant fields
  3. Update README.md
  4. npm publish. You will have to login to npm if you aren't already logged in
  5. Profit!

Commands

  • npm run typecheck: Checks code within src for TypeScript issues. No artifacts are generated
  • npm test: Single test run using Vitest
  • npm run test:watch: Watch mode. Runs all test suites and reruns them when there are changes
  • npm run build: Compiles src into CommonJS and ES modules (along with TypeScript declaration files) into the dist directory
  • npm run verify: Run typechecks + tests + build. Suitable when developing and in CI environments to ensure all checks are valid
  • npm run clean: Deletes the dist directory