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

@seguri/gimme-input

v1.0.0

Published

Get input from command line arguments or unix pipe

Downloads

2

Readme

gimme-input

Installation

npm i -g @seguri/gimme-input

Usage

In your script:

#!/usr/bin/env node
const { gimmeInput } = require('@seguri/gimme-input');

gimmeInput() will now return an array containing either the command line arguments or the lines piped into this script.

Why

I was not satisfied by the existing libraries (commander, minimist, etc.), so why not add more noise.

I took this chance to refresh my knowledge of the javascript ecosystem and write something vaguely useful.

Given this script to-kebab-case:

#!/usr/bin/env node
const { gimmeInput } = require('gimme-input');
const { kebabCase } = require('lodash');
gimmeInput().map(kebabCase).forEach(s => console.log(s));

When it's time to create a new feature branch for your favourite microservice, you can go and copy the relative JIRA ticket title like "BOARD-123: Moar foo" and create a branch out of it:

$ cd /your/git/project
$ git checkout -b $(pbpaste | to-kebab-case)
Switched to a new branch 'board-123-moar-foo'

TODO

An example list of features that may never get implemented:

  • [ ] support \0 line separator
  • [ ] read directly from clipboard to avoid pbpaste | script-using-gimme-input