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

mwe-common-library-client

v6.5.4

Published

React MWE Component for npm

Downloads

292

Readme

mwe-common-library-client

Running the Project

npm install
npm run start

Run Demo

cd demo
npm install
npm run start

Bumping the Package Version

In the main branch, run one of the commands below to bunp the package version. It will update the version in the package.json, package-lock.json, and create a new version tag. It will also automatically commit the changes to those files.

When publishing package versions, please follow semantic versioning.

Major version

Publish a major version when you make incompatible API changes.

npm version major

Minor version

Publish a minor version when you add functionality in a backward compatible manner.

Patch version

npm version minor

Publish a patch version when you make backward compatible bug fixes.

npm version patch

Publishing to Azure DevOps Artifacts

Run git push --follow-tags to push the main branch and tags to remote.

Pushing with a new version tag will trigger a build and deploy the package to Azure DevOps Artifacts.