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

@voltiso/script

v2.0.8

Published

NPM scripts as code.

Downloads

21

Readme

@voltiso/script

NPM scripts as code.

Use in YOUR project

pnpm add -D @voltiso/script

Define some scripts

Create scripts.ts files in your project directory, or any directory above it, e.g.:

// scripts.ts
import { parallel } from '@voltiso/script'

export const build = 'tsc -b'

export const lintEslint = 'eslint .'
export const lintTsc = 'tsc --noEmit'

export const lint = parallel(lintEslint, lintTsc)

export const check = [build, lint] // sequential

export const custom = async () => {
	console.log('custom script')
	return 'pnpm publish' // optional return
}

CLI Usage

pnpm exec v [command]

...or - longer version:

pnpm exec voltiso-script [command]

The script is searched for in this order:

  1. package.json scripts
  2. scripts.ts file in the current directory
  3. scripts.ts file in the parent directory, and so on

Even if the script is found in a directory above, the cwd does NOT change. This allows defining common scripts in a parent directory, instead of duplicating them in every project.