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

releasetrain

v1.4.0

Published

A helper package to improve your CICD workflow and node.js app release process, seek no more with releaseTrain!

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

johnhiggsjohnhiggs

Keywords

Readme

🚂🚃 releaseTrain

🛤️ A node.js helper 📦 to improve your CICD pipeline & app release process, fear no more and bring on the releaseTrain!

Auto cuts a branch based on current source of truth. Creates new branch (RC-version), sets upstream and pushes to origin Notifies via slack

Install

npm add releasetrain

Configure

Add the following short hands to your package.json, and configure the following:

  • appName: your app name (gets included in slack alert)
  • hookUrl: a valid slack incoming webhook token to your workspace
  • channel: a valid channel within the given hookUrl to send notification to (uses slack api)
  • username: (optional) username to send the notification as

More to come...

    "releaseTrain:setConfig": "cd ./node_modules/releasetrain && npm run releaseTrain-config --appName=APP_NAME --hookUrl=INSERT_YOUR_TOKEN_HERE --channel=YOUR_CHANNEL --username=USERNAME --releaseVersion=$npm_package_version",
    "releaseTrain:cut": "cd ./node_modules/releasetrain && npm run releaseTrain-cut --releaseVersion=$npm_package_version",
    "releaseTrain:notify": "cd ./node_modules/releasetrain && npm run releaseTrain-notify",

Set Configuration

you can call your configuration which will generate a json file with the information needed to cut the release and send a notification.

npm run releaseTrain:setConfig

Start the release train!

Now you can run (pulls version from package.json) releaseTrain:cut

This will automatically push up a release train branch of RC-*releaseVersion*

Notifications

You can call npm run releaseTrain:notify within your CI step to slack out the train has been cut!