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

@royalinvest/dto

v0.71.6

Published

Data Transfer Objects (DTOs) to carry data between frontend and backend processes.

Readme

NPM Packages

This project contains shared NPM packages for RoyalInvest (e.g., DTOs, utilities).
Packages are written in TypeScript and published to the company’s NPM organization.


Getting Started

1. Configure NPM registry

To authenticate with the NPM registry, configure your .npmrc file:

npm config set //registry.npmjs.org/:_authToken=<your_auth_token>

Replace <your_auth_token> with a token from npmjs.com.
For access to the company’s account, request a token from the administrator.


Company Packages

You can view all published packages here:
RoyalInvest NPM Packages


Creating a New Package

  1. Create a new directory under npm-package/.
  2. Add:
    • package.json (copy structure from dto/package.json).
    • tsconfig.json (same as in existing packages).
  3. Implement your code in src/.

Each package should follow the same conventions for consistency.


Building a Package

Run the build command inside the package directory:

npm run build

Check the scripts section in dto/package.json for an example configuration.


Versioning

We follow Semantic Versioning (SemVer):

  • MAJOR – incompatible API changes
  • MINOR – add functionality in a backward-compatible manner
  • PATCH – backward-compatible bug fixes

Update the version number manually in package.json before publishing.


Publishing

To publish a package to the NPM registry:

npm publish --access public