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

@myparcel/semantic-release-config

v5.0.1

Published

Reusable configurations for semantic-release

Downloads

113

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

myparcel-nlmyparcel-nledielemoineedielemoinemknijnenbergmknijnenberg

Keywords

semantic-release

Readme

MyParcel semantic-release configuration

npm

This package contains multiple semantic-release presets. Additional information, documentation and guides on semantic-release can be found here

Usage

Install the package via yarn:

yarn add -D @myparcel/semantic-release-config

or npm:

npm i -D @myparcel/semantic-release-config

Create a semantic-release config file, if you haven't already, and add the following: (JavaScript example)

// release.config.js
module.exports = {
  extends: '@myparcel/semantic-release-config',
};

Or to use one of the other available presets:

// release.config.js
module.exports = {
  extends: '@myparcel/semantic-release-config/npm',
};

Configurations

Base config

@myparcel/semantic-release-config

This is the base configuration, which other ones should be based on. For more in-depth information on the configurations used with each plugin, see ./src/plugins/<plugin>.js.

NPM

@myparcel/semantic-release-config/npm

Composer

@myparcel/semantic-release-config/npm

GitHub

@myparcel/semantic-release-config/github

GitHub + Composer

@myparcel/semantic-release-config/github-composer

GitHub + NPM

@myparcel/semantic-release-config/github-npm

Debugging

You can run the following command in your project to test your semantic-release configuration:

npx semantic-release --dry-run --debug --branches=$(git branch --show-current)

Flags used:

  • --dry-run: If this is on, no files are changed and nothing is actually "released".
  • --debug: Enables debug mode to show a lot more output.
  • --branches: Set the current branch as a release branch. If you don't pass this and are not on a release branch semantic-release will not process your commits.