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

batched-semantic-release

v1.1.20

Published

Test project showing how to semantically publish multiple commits to NPM from GitLab

Downloads

11

Readme

batched-semantic-release

Test project showing how to semantically publish multiple commits to NPM from GitLab

Uses semantic-release-gitlab

To publish to NPM use semantic commits and then tag with string that starts with release-.

See .gitlab-ci.yml for actual setup.

Example

This repo has multiple commits at the beginning.

git commit -m "feat(code): test feature 1"
git push origin master
git commit -m "feat(code): test feature 2"
git push origin master
git commit -m "feat(code): test feature 3"
git push origin master

I pushed the commits and the GitLab CI But only the "test" job has executed, not the "deploy" one. Now let us publish this project to NPM by tagging a commit with "release-" string. I prefer using the date

git tag release-2016-08-30

The "deploy" job runs and publishes a version of this package to NPM

npm http 200 https://registry.npmjs.org/batched-semantic-release
+ [email protected]

Now add another commit feat(tag): describe tag example and release it

git tag release-again