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

@figedi/ci-toolkit

v1.9.3

Published

Collection of scripts to be used in our CI pipeline

Downloads

7

Readme

ci-toolkit

This tool is a small wrapper around standard-version to bump projects correctly (release-branches create pre-releases and master-branches create stable-releases)

Usage

Execute the module with npx. See available-commands for a list of supported commands npx @figedi/ci-toolkit:<version> <command> <path>

Available Commands

| Name | Parameters | Intention | |---------------------------|-----------------------------|----------------------------------------| | npm-publish (1st arg) | directory (2nd arg) | npm publish with dist tag support. | | bump (1st arg) | directory (2nd arg) | Changelog and git tag generation. |

Supported env-variables

TICKET_PREFIX. This is optional and falls-back to SHTL. Example usage:

TICKET_PREFIX=DEV npx @figedi/ci-toolkit npm-publish /path/to/repository

TAG_PREFIX. This is optional and falls-back to v. Example usage:

TAG_PREFIX=reponame-v npx @figedi/ci-toolkit npm-publish /path/to/repository

Semantic Commit Messages

** Breaking Changes:**

You can create a breaking change with every message type. You just need to add one \n after your title of the commit message. This should normally be two new lines. If fixed its two new lines.


Message types

| Message | New Version | Example | |-----------|-------------|-------------------------------------------------------------------| | chore: | | chore(build): add build script | | docs: | | docs: added feature for xy SHTL-3122 | | feat: | Minor | feat(commandClass): added new command SHTL-1233 | | fix: | Patch | fix(persisterClass): fixed headache SHTL-123123 | | refactor: | | refactor(main.ts): share logic between 4d3d3d3 and flarhgunnstow | | style: | | style: fixed indendation | | test: | | test(myClass): added unit tests for xyz |

Branch-Management

| Branch | master | release | fix/chore/feature/feat/docs/test | |---------------------------|------------|---------|---------------------------------------| | Release Track | stable | beta | none | | Tests | yes | yes | yes | | Publish image/publish npm | yes | yes | no |