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 🙏

© 2026 – Pkg Stats / Ryan Hefner

exec-ws

v0.2.3

Published

Convert the path to a relative path for the workspace and execute the command within the workspace.

Readme

exec-ws

Convert the path to a relative path for the workspace and execute the command within the workspace.

Install

npm install -D exec-ws

Usage

Call the command by defining the command to be executed and the file in the workspace as arguments.

Detect the file in the workspace from the arguments, convert it to a relative path in the workspace, and execute the command in the workspace.

npx exec-ws {command} {file in workspace}

# (convert to the following)

cd {workspase root}
{command} {file relative path in workspace}

If the arguments include files from other workspaces, execute them in separate workspaces.

npx exec-ws {command} {file-a in workspace-A} {file-b in workspace-B}

# (convert to the following)

cd {workspaseA root}
{command} {file-a relative path in workspace-A}
cd {workspaseB root}
{command} {file-b relative path in workspace-B}

Setup

When executing linter and formatter with pre-commit, you can configure the following settings to coexist with Python tools.

Example: .pre-commit-config.yaml

repos:
  - repo: local
    hooks:
      - id: rye-lint
        name: Rye lint
        entry: rye lint
        language: system
        types: [python]
        description: "Run Python linter"

      - id: rye-fmt
        name: Rye fmt
        entry: rye fmt
        language: system
        types: [python]
        description: "Run Python formatter"

      - id: ts-lint
        name: ESlint (frontend)
        entry: npx exec-ws npx eslint --fix
        language: system
        files: '\.(tsx?|jsx?)$'
        description: "Run Node.js linter"

      - id: ts-fmt
        name: Prettier (frontend)
        entry: npx exec-ws npx prettier --write
        language: system
        files: '\.(tsx?|jsx?|css|json|html)$'
        exclude: '^package-lock\.json$'
        description: "Run Node.js formatter"

Condition

This tool assumes that the "workspaces" is set package.json in the project root.

Example: package.json

{
    "private": true,
    "workspaces": [
        "frontend",
        "packages/*"
    ],
    "devDependencies": {
        "exec-ws": "^0.1.0"
    }
}