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

workspaces-affected

v1.0.15

Published

This tool is providing support for running operations only on affected packages in your [npm workspaces](https://docs.npmjs.com/cli/v7/using-npm/workspaces#defining-workspaces)

Downloads

87

Readme

workspaces-affected

This tool is providing support for running operations only on affected packages in your npm workspaces

Usage:

npx workspaces-affected@latest build --base origin/master

--base flag

base can be any git ref, for example:

npx workspaces-affected build --base COMMIT_ID

npm workspaces support

This example is showing usage of --is-present flag and also passing --coverage to test script:

npx workspaces-affected@latest test --base=origin/master --if-present -- --coverage

github actions example

This workflow will run check for coverage only for affected packages in the workspace:

name: My awesome workflow
on:
  pull_request:
    branches:
      - main
jobs:
  workflow-checks:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - uses: actions/setup-node@v3
        with:
          node-version: 18
      - run: npm install
      - run: npx workspaces-affected@latest test --base=origin/main --if-present -- --coverage

--ignore-private flag

This will ignore private packages (packages.json private: true)

npx workspaces-affected build --base COMMIT_ID --ignore-private

Options

| Flag | Required | Default | Description | |---------------|----------|---------|-------------------------------------------------| | --base | true | master | git ref to compare changes to. | | --with-side | false | false | When true, listing also side affected packages. | | --ignore-private | false | false | When true, private packages will be ignored. | | --ignore-pattern | false | "" | Glob pattern to be ignored when fetching affected files. |