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

@odecloud/components

v0.3.230

Published

Containing useful development UI used by OdeCloud's Platform

Readme

Official site of @odecloud/components

pipeline statusLicense: MIT

Installation

  • Use NPM:
    $ npm install @odecloud/components

Running Unit Tests

You will need node:20-buster. You can use nvm to install the correct version of node. On the root of the project, run the following line:

  • make run-unit-tests

Integration with Chromatic's Storybook

Please read the wiki here in regards to workflow with Chromatic's Storybook.

Publishing to NPM

  1. On the root of the directory, open up package.json
  2. Bump the version by the following guideline:
    • Our version numbering follows Major.Minor.Patch (e.g. 2.10.1)
      • Major: Stable release.
      • Minor: Incremental changes--including new components, remove components, or change of behavior of components.
      • Patch: Small efficient changes--including a fixed to a bug.
    • Note: in regards to Patch if the old functionality was always erroneous, then it will be considered a Patch.
  3. Publish a new tag on the repository by going to https://gitlab.com/odetech/components/-/tags/new.
    • Note: make sure that the "Tag Name" is an exact match to the version inside package.json on step #2.
    • In regards to the "Release notes": we encourage detail and consistent format in order for other developers to understand the new version update.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT