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

@melfore/clibelt

v6.0.5

Published

CLI belt: the Melfore tool belt

Downloads

103

Readme

clibelt

CLI belt: the Melfore tool belt

Usage

Install

npm install @melfore/clibelt

Add scripts to package.json

Add required CLIs to your package.json, for example:

"scripts": {
  "i18n": "i18n-msg",
  "i18n:copy": "i18n-copy --from it --to fr",
  "pwd2hash": "pwd2hash"
}

Configure

There are three ways to configure a CLI.

Clibelt configuration

Create a file .clibelt.json in project root.

Configuration example:

{
  "i18nMsg": {
    "input": "./resources/messages-all-langs.js",
    "outMsg": "./src/messages",
    "outTs": "./src/messages/i18nMessages.ts"
  }
}

Command line arguments

Add arguments to script in package.json, for example:

"scripts": {
  "i18n": "i18n-msg --input new/path --outTs new/constants.ts"
}

Environment variables

Run script with CLI's specific env variables set.

CLIs

i18n-msg

i18n-msg:

  • splits an input file containing all the translations into one file for each language
  • creates a TypeScript source containing a constant for each message.

Configuration

Add i18nMsg to .clibelt.json.

Options

| .clibelt param | command line arg | env variable | Description | Example | | -------------- | ---------------- | ------------ | ------------------------------------------ | ------------------------------ | | input | i18n-input | I18N_INPUT | the input file containing all translations | ./resources/messages-all-langs | | outMsg | i18n-out-msg | I18N_OUT_MSG | splitted messages output directory | ./src/messages | | outTs | i18n-out-ts | I18N_OUT_TS | TypeScript constants output file | ./src/messages/i18nMessages.ts |

Example:

{
  "i18nMsg": {
    "input": "./resources/messages-all-langs.js",
    "outMsg": "./src/messages",
    "outTs": "./src/messages/i18nMessages.ts"
  }
}

pwd2hash

pwd2hash generates an hash for input string

Configuration

No configuration is required, just add to package.json script and run:

npm run pwd2hash string_to_hash

test