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

@corva/fe-dev-helper-cli

v0.7.1

Published

Shared components/utils for Corva ui projects

Downloads

9

Readme

corva-fe-dev-helper-cli

This is a simple CLI that helps with

  • info about latest active branches
  • release/hot fixes
  • releases

Its current goal is to unify our processes. It is very opinionated and supports a single variant workflow.

Requirements to use

Repository should use our auto release config

name: Auto release
on:
  push:
    branches:
      - develop
      - release/[0-9]+.[0-9]+
      - stable/[0-9]+.[0-9]+
  workflow_dispatch:
    inputs:
      release-as:
        description: 'Manually specify new release version'
        required: false

concurrency:
  group: auto-bump-${{ github.ref }}
  cancel-in-progress: true

jobs:
  auto-release:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout source code
        uses: actions/checkout@v4

      - name: Auto release
        uses: corva-ai/gh-actions/core/auto-release@feat/auto-bump-action
        with:
          pr-approver-github-token: ${{ secrets.GH_ACTIONS_AUTOMATION }}
          release-as: ${{ github.event.inputs.release-as }}

Repository should follow our 3envs branching strategy

develop -> create release/X.X -> create stable/X.X repeat

Usage

npx @corva/fe-dev-helper-cli@latest

Contributing

  • checkout from develop (e.g.: git checkout -b feat/TKT-15-my-feature)
  • commit your changes following conventional commits rules
  • create a PR (the name also should follow the same rules)
  • once it's merged - auto version-bump release PR will be created / or existing updated
  • merge the release PR - the new version will be published to NPM

TODO

  • Refactor spaghetti parts, lol
  • Update confirm steps for release assist flow to describe exactly what CLI is going to do, not just release/X.Y - exact versions
  • Add a final confirm step "Open created PRs" that opens all the created PRs, to not have to click on the links
  • Add check that verifies that github actions were actually triggered during the release commands
  • Add tests