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

pishilogger

v2.0.6

Published

helps ypu generate automated changelogs

Downloads

72

Readme

about

this is a small package to help with a simple versioning problem I had at work and speedup manual labor, nevertheless I am open to ideas and hope this would be usefull to anyone who may need it.

envs

also note that this version currently only works with gitlab

{
  "SCOPES": "should be provided as an object with the same key/value pair",
  "PREVIOUS_TAG_SHA": "this is provided in the following yml",
  "CURRENT_TAG_SHA": "this is provided in the following yml",
  "CI_COMMIT_TAG": "this is provided by gitlab ci",
  "GIT_PROJECT_API": "your git project api",
  "GIT_TOKEN": "your PAC or your project access token to read the commits",
  "GIT_PROJECT_URL": "your git project url",
  "CLICK_UP_WORKSPACE_ID": "your click up workspace id, you can see it in the url",
  "CLICK_UP_DOC_ID": "create a doc in click up and see the url for id",
  "CLICK_UP_TOKEN": "genereate a clickup token to upload to clickup",
  "DISCORD_HOOK": "a discord hook",
  "DISCORD_PROJECT_IMG": "an image for prjoect to include in discord message",
  "DISCORD_PROJECT_COLOR_DIGIT": "the color for discord message",
  "DISCORD_NAME": "a name for discord bot",
  "DISCORD_AVATAR": "an avatar for discord bot"
}

and here is the default scope object

{
  "build": "build",
  "ci": "ci",
  "docs": "docs",
  "feat": "feat",
  "fix": "fix",
  "perf": "perf",
  "refactor": "refactor",
  "test": "test"
}

open a pr for any change that you want to be made :)

Also to use this you only need to add a step to your .gitlab-ci.yml file like so:

stages:
  # add this stage before publish
  - changeLogs
update-changelog:
  stage: changeLogs
  image: node:lts-alpine
  rules:
    # change this rule if you follow a different tag format
    - if: '$CI_COMMIT_TAG =~ /^v\d+\.\d+\.\d+$/'
    - when: never
  before_script:
    - apk add --no-cache git
  script:
    # here we set the two commit tags to envs
    - export PREVIOUS_TAG_SHA=$(git rev-list -n 1 $(git describe --abbrev=0 --tags "${CI_COMMIT_TAG}^"))
    - export CURRENT_TAG_SHA=$(git rev-list -n 1 "${CI_COMMIT_TAG}")
    - npx pishilogger