New Nx Repository

✨ Your new, shiny Nx workspace is ready ✨.

Learn more about this workspace setup and its capabilities or run npx nx graph to visually explore what was created. Now, let's get you up to speed!

Try the full Nx platform

🚀 If you haven't connected to Nx Cloud yet, complete your setup here. Get faster builds with remote caching, distributed task execution, and self-healing CI. See how your workspace can benefit.

Generate a library

npx nx g @nx/js:lib packages/pkg1 --publishable --importPath=@my-org/pkg1

Run tasks

To build the library use:

npx nx build pkg1

To run any task with Nx use:

npx nx <target> <project-name>

These targets are either inferred automatically or defined in the project.json or package.json files.

More about running tasks in the docs »

Versioning and releasing

To version and release the library use

npx nx release

Pass --dry-run to see what would happen without actually releasing the library.

Learn more about Nx release »

Keep TypeScript project references up to date

Nx automatically updates TypeScript project references in tsconfig.json files to ensure they remain accurate based on your project dependencies (import or require statements). This sync is automatically done when running tasks such as build or typecheck, which require updated references to function correctly.

To manually trigger the process to sync the project graph dependencies information to the TypeScript project references, run the following command:

npx nx sync

You can enforce that the TypeScript project references are always in the correct state when running in CI by adding a step to your CI job configuration that runs the following command:

npx nx sync:check

Learn more about nx sync

Nx Cloud

Nx Cloud ensures a fast and scalable CI pipeline. It includes features such as:

• Remote caching
• Task distribution across multiple machines
• Automated e2e test splitting
• Task flakiness detection and rerunning

Set up CI (non-Github Actions CI)

Note: This is only required if your CI provider is not GitHub Actions.

Use the following command to configure a CI workflow for your workspace:

npx nx g ci-workflow

Learn more about Nx on CI

Install Nx Console

Nx Console is an editor extension that enriches your developer experience. It lets you run tasks, generate code, and improves code autocompletion in your IDE. It is available for VSCode and IntelliJ.

Install Nx Console »

Useful links

Learn more:

• Learn more about this workspace setup
• Learn about Nx on CI
• Releasing Packages with Nx release
• What are Nx plugins?

And join the Nx community:

• Discord
• Follow us on X or LinkedIn
• Our Youtube channel
• Our blog

Usage

Run without installing:

npx @jandersoncampelo/claude-inspector@latest

This starts a local server, opens your browser, and shows an inspector for your ~/.claude directory.

Flags:

• --port <n> — use a fixed port (default: an automatic free port)
• --dir <path> — inspect a different Claude directory (default: ~/.claude)
• --no-open — don't open the browser automatically

Every tagged release also attaches a tarball, so the registry is not a hard dependency:

npx https://github.com/jandersoncampelo/claude-inspector/releases/download/v0.1.0/claude-inspector-0.1.0.tgz

Local development

• npm run dev — build and serve the app (same mode npx @jandersoncampelo/claude-inspector uses), via npx nx serve server.
• npm run build — build the server + frontend bundles, via npx nx build server.
• npm run package — assemble the publishable npm package into dist/publish/, via npx nx package server.

Releasing

Publishing is automated by .github/workflows/release.yml: pushing a v* tag builds the package, publishes it to npm, and creates a GitHub Release with the tarball attached. The tag is the source of truth for the version — scripts/make-publish-package.mjs reads it from PACKAGE_VERSION, so the root package.json version is only a local fallback.

One-time setup: create an npm Automation access token and store it as the repository secret NPM_TOKEN (Settings → Secrets and variables → Actions).

Then, to cut a release:

git tag v0.2.0 && git push origin v0.2.0