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

cross-release-cli

v0.0.1-alpha.5

Published

command line app for cross language bump utility

Downloads

7

Readme

Cross Release CLI

Usage

  1. install through package manager
# pnpm
pnpm i cross-release -g

otherwise you can use you favorite package manager instead

# npm
npm i cross-release -g
# yarn
yarn add cross-release --global
  1. add to your package.json
{
  "scripts": {
    "release": "cross-release"
  }
}
  1. run release script
pnpm run release

Command line

| short | long | description | default | | ----- | --------------- | --------------------------------------------------- | -------------------------- | | -m | --main | Main project language e.g. java / javascript / rust | false | | -r | --recursive | Run the command for each project in the workspace | false | | -d | --dry | Dry run | false | | -D | --dir [dir] | Set working directory | project root | | -c | --commit | Commit current changes | false | | -p | --push | Push the project to remote | false | | -t | --tag | Create a tag for current version | false | | -e | --exclude [dir] | Folders to exclude from search | ["node_modules", ".git"] | | -y | --yes | Answer yes to all prompts | false |

Configuration

You can specify various runtime settings by using the "package.json" file. Here are some examples that cover all the parameters:

{
  "...": "...",
  "cross-release": {
    // show the help message
    "showHelp": false,
    // show the version about cross-release
    "showVersion": false,
    "version": "",
    "isAllYes": false,
    "isDry": false,
    "isRecursive": false,
    "shouldCommit": false,
    "shouldPush": false,
    "shouldTag": false,
    // default exclude folders are `["node_modules", ".git"]`, your config will be append within it
    "excludes": ["path/to/exclude"],
    "dir": "/path/to/run",
    "commit": {
      // Whether to invoke git pre-commit and commit-msg hook
      "shouldVerify": true,
      // Whether to stage all un-staged files or stage only changed files
      "shouldStageAll": false,
      // the symbol '%s' will be replace to the version number that you specified
      "template": "chore: release v%s"
    },
    "push": {
      "shouldFollowTags": false
    }
  }
}