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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@opuscapita/dashboard-widgets

v1.4.1

Published

Dashboard widgets components library.

Downloads

38

Readme

Development

Run library locally:

Make sure you use node 14 (node -v to check)

  1. Run npm install to install dependencies
  2. Run npm run dev to start the development server
  3. In local/index.tsx there's a local playground for the library. Import the components you want to test and use them in the playground. Do not commit this file.

Run tests

Make sure you use node 14 (node -v to check)

  • Run npm run test to run the tests
  • Run npm run test:ui to run UI for the tests

Linting

  • Run npm run lint to run the linter
  • Run npm run lint:fix to run the linter and fix errors
  • This library uses husky and lint-staged to run the linter on pre-commit

Run package in other project

  1. (Optionally) Run npm run release:dry to report what would have done, if you publish the package
  2. Run npm pack to create a tarball
  3. Go to the project you want to test the package in and run npm i -D <path to tarball>, e.g.: npm i -D '~/Desktop/dashboard-widgets/dashboard-widgets-0.0.1.tgz'

Publishing

  1. Make sure you are logged in to npm with the npm whoami, and you are added to OpusCapita npm registry
  2. Make sure your working directory is clean
  3. Run npm run release to publish the package
  4. Follow the steps in the terminal

Contributing

  1. Create a branch feature/BNAPP-<ticket number>_<short description>
  2. On the branch, make your changes
  3. Create tests and stories for each new component / use case if applicable
  4. Run npm run test to make sure all tests pass
  5. Commit those changes and create meaningful pull request
  6. After PR is approved, merge it to master
  7. Release the package to npm according to the Publishing instruction above