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

@thangha/release-document

v1.0.5

Published

The feature to prepare and announce the release document.

Downloads

1

Readme

Release document Package

This package is used to trigger function to prepare, sign-off and announce the release document.

Configurations:

  1. step 1: Add this package into the package.json file of repo you want to use
  2. step 2: Generate the corresponding package-lock.json (ensure that new image will be build successfully)
  3. step 3: Add these 3 line bellow into the package.json file and continue remain steps for each step (generate document, sign-off, announce document)
    {
        ...
        "scripts": {
            ...
            "prepare-release-doc": "prepare-release-doc",
            "sign-off": "sign-off",
            "announce-release-doc": "announce-release-doc"
        }        
    }

GENERATE DOCUMENT:

  1. use command npm run prepare-release-doc --argName2=value1 instead
  2. param list:
    • repoName: string, required
repoName="mmgp-micro-frontend-messaging"

docker run \
-v ~/.ssh:/root/.ssh \
...
-w="/code" \
$(buildkite-agent meta-data get "image-version") \
bash -c "${SOURCE_MOVING} \
  && echo '--- :js: Fetching branches origin/${BUILDKITE_BRANCH} and origin/${BUILDKITE_PULL_REQUEST_BASE_BRANCH}' \
  && git fetch origin ${BUILDKITE_BRANCH} && git fetch origin ${BUILDKITE_PULL_REQUEST_BASE_BRANCH} \
  && npm run prepare-release-doc -- \
  ...
  --repoName=${repoName} \
  --slackToken=${SLACK_TOKEN}"

SIGN-OFF:

  1. use command npm run sign-off --argName2=value1 instead
  2. param list:
    • serviceName: string, required
    • repoName: string, required
    • recipient: string, required
    • serviceOwner: string, required
    • changeOwner: string, required
    • slackChannel: string, required
serviceName="HUB Inbox MFE"
repoName="mmgp-micro-frontend-messaging"
recipient="<@U02B9519VA6>"
serviceOwner="<@U02B9519VA6>"
changeOwner="<@U02B9519VA6>"
slackChannel="C03A9ALDD9U"

docker run \
-v ~/.ssh:/root/.ssh \
...
$(buildkite-agent meta-data get "image-version") \
bash -c "${SOURCE_MOVING} \
  && echo '--- :js: Fetching branche origin/${BUILDKITE_BRANCH}' \
  && git fetch origin ${BUILDKITE_BRANCH} \
  && npm run sign-off -- \
    --source=origin/${BUILDKITE_BRANCH} \
    --repoName=${repoName} \
    --serviceName=${serviceName} \
    --recipient=${recipient} \
    --serviceOwner=${serviceOwner} \
    --changeOwner=${changeOwner} \
    --slackChannel=${slackChannel} \
    --slackToken=${SLACK_TOKEN}"

ANNOUNCE DOCUMENT:

  1. use command npm announce-release-doc --argName2=value1 instead
  2. param list:
    • repoName: string, required
repoName="mmgp-micro-frontend-messaging"

docker run \
-v ~/.ssh:/root/.ssh \
-v ${SSH_AUTH_SOCK}:/ssh-agent \
-v ${PWD}:${MOUNTED_DIR} \
-e "SSH_AUTH_SOCK=/ssh-agent" \
-e "BUILDKITE_BRANCH" \
-e "SLACK_TOKEN" \
-e "HUSKY" \
-w="/code" \
$(buildkite-agent meta-data get "image-version") \
bash -c "${SOURCE_MOVING} \
  && echo '--- :js: Fetching branche origin/${BUILDKITE_BRANCH}' \
  && git fetch origin ${BUILDKITE_BRANCH} \
  && npm run announce-release-doc -- \
  --source=origin/${BUILDKITE_BRANCH} \
  --repoName=${repoName} \
  --slackToken=${SLACK_TOKEN} "