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

@-xun/changelog

v0.3.4

Published

A conventional-changelog-core fork with bug fixes and support for multiple tag formats

Downloads

696

Readme

Black Lives Matter! Last commit timestamp Codecov Source license Uses Semantic Release!

NPM version Monthly Downloads

xchangelog (@-xun/changelog)

This conventional-changelog-core fork slightly tweaks the original to fix some bugs and bundle type definitions that are more well-formed.

Among the bugs fixed by this fork is one where conventional-changelog-core, when given a release commit with multiple tags, will only accept the first tag in the list as the version tag if it matches (i.e. starts with tagPrefix). Without this fix, when the actual matching version tag is not first in the list, strange things happen.

Multiple tags on the same release commit is useful when, for instance, you transmute a polyrepo into a monorepo and need to alias the original v${version}-style tags with the more monorepo-friendly ${package-name}@${version}-style tags.

[!NOTE]

The only reason to use xchangelog over conventional-changelog-core is if you are using an xscripts-powered project or you need the bug fixes. Otherwise, just use conventional-changelog.

Install

To install xchangelog:

npm install --save-dev @-xun/changelog

If you want to use a specific version of xchangelog, provide its semver:

npm install --save-dev @-xun/[email protected]

[!NOTE]

xchangelog installations can reuse the "conventional-changelog-core" name so that plugins with conventional-changelog-core as a peer dependency are able to recognize xchangelog's presence. For example:

npm install --save-dev conventional-changelog-core@npm:@-xun/changelog

Usage

import conventionalChangelogCore from '@-xun/changelog';

conventionalChangelogCore().pipe(process.stdout); // or any writable stream

See the conventionalChangelogCore upstream documentation for more details.

Contributing

Consider contributing to upstream conventional-changelog instead.