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

epersonam-notification-client

v0.14.0

Published

Client JS Notification library

Downloads

98

Readme

Notification Client

Provides the UI components to list notifications.

WARNING: Before committing please run yarn so the dist package gets updated!

Publish

  1. Bump the package.json version.
  2. Update CHANGELOG.md with changes.
  3. Merge to Master branch: the pipeline will deploy your new version in https://www.npmjs.com/package/epersonam-notification-client

note: during a PR, the pipeline checks if you did update both CHANGELOG.md and package.json. If not gives an error.

Manual Publish (old way, deprecated)

  1. Bump the package.json version.
  2. Update CHANGELOG.md with changes.
  3. Publish to NPM registry: 1. Login to NPM: npm login. 2. Publish to NPM: npm publish

Install

Run the following, also whenever you want to update to latest version as we currently don't go with npm registry.

yarn add epersonam-notification-client

Work locally

If you want to avoid deploying this repo everytime you need to test a change you can use the local version of the npm package.

Old method

  1. Each time you change this project you have to hit yarn
  2. on the client run something like yarn add file:../epersonam-notification-client

New method

(see: https://classic.yarnpkg.com/en/docs/cli/link/)

  1. Run from this project yarn link
  2. Go to project where notification-client is used (i.e.: epersonam) and run yarn link "epersonam-notification-client": this action will cause that project too use the local copy of the package, instead of the one versioned and published from remote repo.
  3. When finished, just run yarn unlink "epersonam-notification-client.