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

@enterprise-cmcs/mdct-core

v0.2.2

Published

Core functionality used across CMS MDCT applications

Downloads

4

Readme

@enterprise-cmcs/mdct-core

npm version Maintainability Test Coverage

How to publish this package to npm

The mdct-core npm package uses semantic-release to publish packages to the enterprise-cmcs npm org. To read more about semantic release please visit the following link: https://github.com/semantic-release/semantic-release

The publish workflow will run only when pull requests are merged into the main branch and the mechanism for publishing relies on the commit message to trigger a publishing build based on a few key words.

the 3 keywords for semantic release are as following:

  • "fix": this will up the patch version of the release number (note: semantic release calls patch a fix release)

  • "feat": this will update the minor version of the release number (note: semantic release calls this a feature release)

  • "perf": this will update the major version of the release number (note: semantic release calls this a breaking release)

For example:

fix(publishing from CI): my commit message of choice

note: the commit message needs to be on the merge commit when merging into main