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

kemaro-common-components

v2.3.3

Published

KEMARO web-app common components

Downloads

634

Readme

KEMARO web-app common components

kemaro-common-components NPM package Some reusable components, hooks and interfaces are being maintained in the NPM package kemaro-common-components (allows sharing of components between apps)

In order to make changes / add components to the package, follow these steps:

  1. Clone this repository
  2. If you're not a package maintainer yet: create an NPM account and request an existing maintainer ("Who do I talk to?") to invite you as a package maintainer (write access)
  3. Implement your changes or add new elements (components, hooks, interfaces). If you add something new, make sure to export it in index.ts (project root)
  4. Update the package version number (increment minor version if no breaking changes, otherwise increment major version)
  5. If you're not logged in to npm yet, log in: npm login
  6. Prepare for publishing, check for errors, ensure only necessary files are included in the package: npm publish --dry-run
  • this will also lint / build (see prepublishOnly in package.json, which runs before publishing)
  • this will not yet publish to npmjs
  • below Tarbal Contents, only files listed in package.json->files should be included
  1. If everything is okay, publish: npm publish check kemaro-common-components for the new version
  2. In order to get your changes in the micro-frontend projects, update to / install the new npm package version for kemaro-common-components (in package.json AND package-lock.json)

(the above instructions are mostly based on this tutorial, using npm install instead of yarn)