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

scrif

v0.2.0

Published

simple ternaries in npm scripts

Downloads

323

Readme

scrif

simple ternaries in npm scripts

install

npm i -D scrif

use

to use scrif, add it to npm scripts, e.g.

"start": "scrif dev ? npm run dev : npm run production ?"

then, you can pass strings that match the args in scrif to run the branch, e.g.

npm run start dev

syntax

scrif [conditions] ? [branch a] : [branch b] ?

Note that the trailing question mark is required.

complexity

You can use any number of search terms but all must match

"cmd": "scrif arg1 arg2 ? ./script-a.sh : ./script-b.sh ?"

will run branch a with: npm run cmd arg1 arg2 but not npm run cmd arg1

You can pass additional args and they will be passed along to both branches

given

"cmd": "scrif a ? ./script-a.sh : ./script-b.sh ?"
npm run cmd foo bar a

will execute ./script-a.sh foo bar

Order doesn't matter, conditions will be removed from args one time. So for instance:

npm run cmd a a

will execute ./script-a.sh a