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

nx-ignore

v19.8.0

Published

This package is used on platforms such as Netlify or Vercel to ignore builds if a project is not affected.

Downloads

174,425

Readme

nx-ignore

This package is used on platforms such as Netlify or Vercel to ignore builds if a project is not affected.

Usage

npx nx-ignore <project-name>

For Netlify, use a custom ignore command in your netlify.toml file.

For Vercel, under the Settings > Git section, use this script in Ignored Build Step field.

Options

  • --additional-packages - List of additional npm packages to install when using --slim-install. Use this for packages required in configuration files that infer Nx targets (e.g. @playwright/test). Defaults to a list of known packages required by Nx and Nx plugins.
  • --base - Set a custom base SHA to compare changes (defaults to CACHED_COMMIT_REF on Netlify or VERCEL_GIT_PREVIOUS_SHA on Vercel).
  • --plugins - List of Nx plugins required (i.e. plugins that extend the Nx graph). Default plugins are read from nx.json.
  • --root - Set a custom workspace root (defaults to current working directory).
  • --slim-install - Install only Nx and necessary plugins to speed up the script (defaults to true when not using plugin, and false when plugins are used).
  • --verbose - Log more details information for debugging purposes.

Skipping and forcing deployment

Skip nx-ignore check and ignore deployment:

  • [skip ci]
  • [ci skip]
  • [no ci]
  • [nx skip ]

Skip nx-ignore check and force deployment:

  • [nx deploy]
  • [nx deploy ]

How it works

The nx-ignore command uses Nx to determine whether the current commit affects the specified app. It exits with an error code (1) when the app is affected, which tells the platform to continue the build, otherwise it exits successfully, which tells the platform to cancel the build.

Troubleshooting

Error Failed to process project graph occurs on Netlify

When plugins are used in nx.json, Nx infers projects and targets through those plugins via their corresponding configuration files. For example, @nx/next/plugin infers projects and targets from next.config.js files. This means that modules imported in next.config.js must be present in order for Nx to work correctly.

If you run into the Failed to process project graph error, it means that some of the packages are missing. To debug what packages are missing, run npx nx-ignore@latest <app> --verbose --slim-install locally, and you should see an error with the missing package. You can also run npx nx show projects to debug any missing packages, after running the npx nx-ignore command.

Use the --additional-packages option to install the missing packages as detected above. For example,

npx nx-ignore@latest <app> --verbose --slim-install --additional-packages=@playwright/test,jest-environment-jsdom