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

@technologiestiftung/semantic-release-config

v1.2.4

Published

A sharable semantic release config

Downloads

1,137

Readme

All Contributors

shareable semantic-release-config

shareable semantic-release-config

Installation

npm install @technologiestiftung/semantic-release-config

Usage

Add file called release.config.js to your repo

module.exports = {
	extends: "@technologiestiftung/semantic-release-config",
};

If you use a staging/production environment, where staging is the branch staging and production is deployed from main it is wise to add an additional package to do some backmerging. Install it using npm npm i -D @saithodev/semantic-release-backmerge and add it as a plugin to your config, referencing the right branches.


 branches: [
        { name: "main" },
        { name: "staging", channel: "pre/rc", prerelease: "rc" }, // `prerelease` is built with the template `${name.replace(/^pre\\//g, "")}`
    ],
plugins: [
		[
			"@saithodev/semantic-release-backmerge",
			{
				branches: [{from: "main", to: "staging"}],
				backmergeStrategy: "merge",
			},
		],
	],

Overwrite possible keys. See the semantic-release docs. If operating with protected branches, you can need to set the option persist-credentials: false in your workflow file on the actions/checkout@v3 step.

steps:
  - uses: actions/checkout@v3
    with:
      persist-credentials: false

See also this repos .github/workflows/test-and-release.yml how to use this in GitHub Actions.

Needs a Personal Access Token with repo scope to be set as GH_TOKEN in the repo secrets and a NPM_TOKEN with write scope.

Development

Do your thing. Early stages.

Contributors

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

Content Licensing

Credits

Related Projects