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

@nx-devkit/nx-cloud

v0.0.17

Published

Nx plugin that adds an nx-cloud-rotate target to the workspace root — rolls over to a fresh Nx Cloud organization when quota is exhausted.

Readme

@nx-devkit/nx-cloud

Zero-config Nx plugin that puts an nx-cloud-rotate target on the workspace root project. The target creates a fresh Nx Cloud organization + workspace (same name, new binding — nxCloudId, or nxCloudAccessToken on the v1 fallback) and rebinds nx.json — the escape hatch for when your Nx Cloud quota is exhausted and you want to roll over to a new org.

Install

bun add -D @nx-devkit/nx-cloud
bunx nx g @nx-devkit/nx-cloud:init   # registers the plugin in nx.json

or register manually:

// nx.json
{ "plugins": ["@nx-devkit/nx-cloud"] }

Usage

bunx nx run <root-project>:nx-cloud-rotate
# or with options
bunx nx run <root-project>:nx-cloud-rotate --workspaceName=my-workspace --dryRun

What it does:

  1. Reads the current binding (nxCloudId / nxCloudAccessToken) from nx.json.
  2. POST {cloudUrl}/nx-cloud/v2/create-org-and-workspace — the same endpoint nx connect-to-nx-cloud calls ({cloudUrl} defaults to https://cloud.nx.app, override via option or env). Falls back to {cloudUrl}/nx-cloud/create-org-and-workspace (v1) on HTTP 404.
  3. Writes the returned nxCloudId (or nxCloudAccessToken on v1) into nx.json, removing the stale counterpart key.
  4. Prints the onboarding URL so you can claim the org in the Nx Cloud dashboard.

Deleting the old organization

There is no public API or CLI command to delete an Nx Cloud organization — the server swagger was removed from the docs explicitly. Delete it manually at https://cloud.nx.app (organization settings → danger zone), or leave it: an exhausted free org costs nothing. The previous binding is reported once, masked to its first four characters, and is not persisted — enough to spot the old org in the dashboard list; the full value is unrecoverable once nx.json is rewritten.

Options

| Option | Type | Default | Description | |---|---|---|---| | workspaceName | string | root package.json name | Name sent to create-org-and-workspace | | cloudUrl | string | NX_CLOUD_API/NRWL_API env or https://cloud.nx.app | Nx Cloud instance URL | | installationSource | string | nx-devkit-nx-cloud | Telemetry tag sent with the request | | dryRun | boolean | false | Call the API but do not rewrite nx.json |

Notes

  • Works unauthenticated — same trust level as nx connect-to-nx-cloud. The created org is unclaimed until you open the onboarding URL.
  • If your old org was GitHub-connected, the replacement is a standard org; VCS integration must be re-linked in the dashboard.
  • Committing nx.json after rotation points CI at the new org immediately. Warning: the default nxCloudId grants read-write remote-cache access to anyone holding it — on public repos the committed ID is world-visible, so anyone can read and write your Nx Cloud cache. If that matters, rotate the org's access-level in the Nx Cloud dashboard or keep the repo private.