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

@tablecheck/semantic-release-config

v7.2.0

Published

Configuration for creating gitlab releases for TableCheck applications in a sensible format

Downloads

47

Readme

@tablecheck/semantic-release-config

A semantic-release config, used with our commitlint settings and does the following steps.

  1. Increments the version according to conventional-commits.
  2. Publishes a "GitHub Release" with correctly linked JIRA tickets.
  3. Publishes a message to a slack webhook.
  4. Outputs the new version to version.txt for ease of use in other reports.

Required CI Variables

| Variable | Usage | Where to get it from | | ------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | GITHUB_TOKEN | API Token Used for parsing previous releases and publishing the new one | Available in semaphoreci github-releases secret or see https://github.com/semantic-release/github#github-authentication | | SLACK_WEBHOOK | Used for posting slack updates | Go to the Semantic Release App and generate a new webhook for the channel you wish to post to. https://api.slack.com/apps/A021U4J1CQ4/incoming-webhooks |

Usage

Setup the configuration file of semantic-release as follows. For more details on configuration see here (link).

To run a release, simply run npx semantic-release (semantic-release is a required peer-dependency)

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

If your release also needs to publish an npm package, use the following config. Refer to the @semantic-release/npm docs for required environment variables and setup.

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