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

@saroj-parajuli/spsdesign

v0.1.0

Published

Shared SPS design system package with MUI exports, theme helpers, animations, and Sass assets.

Readme

SPSDESIGN

@saroj-parajuli/spsdesign is the shared SPS design system package extracted from the auth app design folder.

It currently ships:

  • centralized MUI component exports
  • shared icon exports and icon lookup helpers
  • reusable MUI theme objects and style helpers
  • Sass tokens, mixins, utilities, and shared auth styles

Install

Local workspace usage

{
  "dependencies": {
    "@saroj-parajuli/spsdesign": "file:../design"
  }
}

Then run npm install in the consuming project. If your local clone lives elsewhere, replace ../design with the correct relative path to this repository.

GitHub usage

{
  "dependencies": {
    "@saroj-parajuli/spsdesign": "git+https://github.com/saroj-parajuli/design.git#main"
  }
}

For SSH-based installs:

{
  "dependencies": {
    "@saroj-parajuli/spsdesign": "git+ssh://[email protected]/saroj-parajuli/design.git#main"
  }
}

Use

MUI exports

import { Box, Button, Typography } from '@saroj-parajuli/spsdesign/mui';

Theme exports

import { ThemeProvider, CssBaseline, theme } from '@saroj-parajuli/spsdesign/theme';

Sass entrypoint

@use '@saroj-parajuli/spsdesign/sass' as *;

Build

npm install
npm run build

The build outputs TypeScript bundles to dist/ and copies the raw Sass assets to dist/sass/.

Publish To npm

Before publishing, confirm that you own the npm scope used by the package name.

Current package name:

"name": "@saroj-parajuli/spsdesign"

If you do not own the @saroj-parajuli scope on npm, rename the package before publishing.

Validate the package contents

npm run build
npm pack

Publish

npm login
npm whoami
npm publish --access public

Because the package is scoped, public publishing requires --access public.