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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pkg-typescript-plugin-scripts

v0.2.12

Published

[![npm version](https://badge.fury.io/js/pkg-typescript-plugin-scripts.svg)](https://badge.fury.io/js/pkg-typescript-plugin-scripts) [![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC) [![TypeScript](h

Readme

Scripts plugin for pkg-typescript

npm version License: ISC TypeScript

A pkg-typescript plugin that automatically generates npm scripts for files in a scripts directory, with configurable runners for different file types.

Overview

This plugin scans a specified directory for script files and automatically generates npm scripts based on the file names and their extensions. It supports multiple file types through configurable runners, making it easy to execute TypeScript, Python, JavaScript, shell scripts, and more directly through npm scripts.

Features

Automatic Script Generation

  • Scans a configurable directory (default: scripts) for script files
  • Generates npm script names based on file names (converts underscores to hyphens, lowercases)
  • Supports multiple file extensions through configurable runners

Configurable Runners

Map file extensions to their execution commands:

  • .ts files → tsx (TypeScript execution)
  • .py files → python (Python scripts)
  • .js files → node (JavaScript execution)
  • .sh files → bash (Shell scripts)
  • Any custom file type with appropriate runner

Smart Naming

  • Converts file names to kebab-case npm script names
  • Example: build_database.tsbuild-database script
  • Example: Deploy_App.pydeploy-app script

Usage

Add this plugin to your pkg-typescript configuration:

export default {
  plugins: ['scripts'],
  config: {
    pkg_ts: {
      scripts: {
        dir: 'scripts', // optional, defaults to 'scripts'
        runners: {
          ts: 'tsx',
          py: 'python',
          js: 'node',
          sh: 'bash',
        },
      },
    },
  },
}

Configuration

The plugin accepts these configuration options:

dir (optional)

  • Type: string
  • Default: 'scripts'
  • Description: Directory to scan for script files

Examples:

  • "./scripts"
  • "src/scripts"
  • "tools"

runners (required)

  • Type: Record<string, string>
  • Description: Maps file extensions to their execution commands

Example:

{
  "ts": "tsx",        // TypeScript files
  "py": "python",     // Python files
  "js": "node",       // JavaScript files
  "sh": "bash",       // Shell scripts
  "rb": "ruby",       // Ruby scripts
  "go": "go run"      // Go files
}

Example

Given this directory structure:

scripts/
├── build_database.ts
├── deploy_app.py
├── cleanup.sh
└── generate_docs.js

With this configuration:

{
  dir: 'scripts',
  runners: {
    'ts': 'tsx',
    'py': 'python',
    'sh': 'bash',
    'js': 'node'
  }
}

The plugin generates these npm scripts:

{
  "build-database": "tsx scripts/build_database.ts",
  "deploy-app": "python scripts/deploy_app.py",
  "cleanup": "bash scripts/cleanup.sh",
  "generate-docs": "node scripts/generate_docs.js"
}

Run them with:

npm run build-database
npm run deploy-app
npm run cleanup
npm run generate-docs

Development

yarn pkg:build    # Build the plugin
yarn install      # Install dependencies

License

ISC