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

@weave-framework/nx

v3.4.1

Published

Nx plugin for Weave — inferred build/serve/check targets (crystal createNodesV2), executors, and generators, so a Weave app is a first-class project in an Nx monorepo.

Readme

@weave-framework/nx

An Nx plugin that makes a Weave app a first-class project in an Nx monorepo — inferred targets, executors, and generators. Drop it into an existing Nx workspace and your Weave apps get Nx caching, nx affected, and the project graph with zero hand-wiring.

Install

nx add @weave-framework/nx
# or: npm i -D @weave-framework/nx  and add the plugin to nx.json (below)

Register the inference plugin in nx.json:

{
  "plugins": ["@weave-framework/nx/plugin"]
}

Inferred targets (crystal)

For every weave.config.{ts,js,json} in a project, the plugin infers three targets — no project.json boilerplate:

| Target | Runs | Cached | |--------|------|--------| | build | weave build (output = the config's outDir) | ✓ | | serve | weave dev (watch + live-reload) | — | | check | weave check | ✓ |

nx build my-app
nx serve my-app
nx check my-app

Each target runs the existing weave CLI with cwd set to the project root, so it resolves that project's own config — the Weave CLI itself needs no Nx-specific changes.

Override the inferred target names in nx.json if they collide with another plugin:

{ "plugins": [{ "plugin": "@weave-framework/nx/plugin", "options": { "buildTargetName": "bundle" } }] }

Generators

nx g @weave-framework/nx:application my-app          # a Weave app project (+ build/serve/check)
nx g @weave-framework/nx:library ui-kit              # a component library (imported from source)
nx g @weave-framework/nx:component UserCard --project my-app   # a component into a project

Executors (explicit wiring)

Prefer explicit project.json targets over inference? The same three are available as executors: @weave-framework/nx:build, :serve, :check.

Zero-dependency note

@nx/devkit is a dev-time dependency of this plugin — correct and unavoidable for an Nx plugin (it's tooling, only pulled in by Nx users). The Weave runtime, compiler, and router stay zero-dependency; the executors shell out to the existing weave CLI rather than re-implementing the build.

📚 Guides + full API reference: Tooling guide

License

MIT