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

@webpieces/nx-webpieces-rules

v0.3.145

Published

Nx-specific webpieces validation rules and graph tooling. Bundles all @webpieces rule packages with Nx graph validators and an inference plugin.

Readme

@webpieces/nx-webpieces-rules

Nx inference plugin that auto-creates webpieces validation targets (architecture graph checks, code-size/style rules, and a per-project circular-import gate) without any manual project.json wiring.

Add it to nx.json:

{
  "plugins": ["@webpieces/nx-webpieces-rules"]
}

Circular file-import gate (validate-no-file-import-cycles)

Each project gets a validate-no-file-import-cycles target that runs madge over its TypeScript sources and fails on an import cycle. madge is bundled as a pinned dependency, so there is no runtime npx fetch (which previously corrupted CI npx caches).

It is wired into the build: the @nx/js:tsc target default lists it in dependsOn, so nx affected --target=ci (→ cibuild) and nx run-many --target=build both run it.

Configuration

On/off and a time-boxed grace window come from webpieces.config.json at the workspace root — the same source of truth as every other webpieces rule — under the rule key no-file-import-cycles:

{
  "rules": {
    "no-file-import-cycles": {
      "mode": "ON",                            // "OFF" disables the gate everywhere
      "ignoreModifiedUntilEpoch": 1771931925,  // epoch SECONDS — while now < epoch,
                                               //   cycles are REPORTED but the build
                                               //   PASSES; after it, the gate fails again
      "ignoreTypeOnly": false                  // when true, ignore `import type`
                                               //   re-export cycles (erased at compile
                                               //   time, harmless at runtime)
    }
  }
}

Semantics, mirroring the method/file-size dated-disable model:

| Situation | Result | | ------------------------------------------- | ------------------------------- | | mode: "OFF" | Skipped (passes), no madge run | | Cycle found, no ignoreModifiedUntilEpoch | Fails | | Cycle found, now < ignoreModifiedUntilEpoch | Reported but passes (warn) | | Cycle found, now >= ignoreModifiedUntilEpoch | Fails again | | No cycle | Passes |

The grace window lets you turn a strict gate on against an existing codebase without an open-ended "off everywhere" escape hatch — the debt can't be silently forgotten because the gate starts failing again after the date.

Disabling at the Nx layer

Setting circularDeps.enabled: false in the plugin options removes the target entirely (rather than toggling it via config). Prefer mode: "OFF" instead — it keeps the target present so any dependsOn references don't dangle.