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

@cludosearch/cludo-search-components

v1.0.36

Published

Cludo Search Components in React

Downloads

783

Readme

Getting Started

Local development

Option 1

  1. Run npm build or npm run dev from cludo-search-components project
  2. Run npm link
  3. Open vs code folder to solution in which you want to use your local component development
  4. Run npm link @cludosearch/cludo-search-components

You should now be using your locally developed shared library in the project that has it as a dependency

Option 2

You can reference this library locally by adding the local package to an NPM configuration.

npm install --save ./../cludo-search-components

Publishing a new version

In order to publish a new package, the version number must be updated. Make sure to update this by running npm version [ major | minor | patch ] on your PR branch. Documentation for this command can be found here.

Running Storybook locally

Versions 0.18.3+ of the component library include Storybook documentation of components. To build and run Storybook locally, make sure you have updated packages with npm install and then run npm run storybook.