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

@cadcamfunv2/cadcamfun-nikcli-plugin

v0.1.41

Published

Drive a running CADCAMFUN instance from a standalone nikcli: the application's CAD/CAM action catalogue as nikcli tools.

Readme

@cadcamfunv2/cadcamfun-nikcli-plugin

A standalone nikcli (terminal, another machine, CI) driving a running CADCAMFUN: the application's CAD/CAM action catalogue as nikcli tools. Same tool ids and descriptions as the in-app assistant (cad, cad_edit, cam, cam_edit, library, parts, library_edit, memory, memory_edit, research, vcs, vcs_edit), each carrying its actions behind action.

The list is read from the running application (GET /api/ai/actions), so the plugin never holds a second copy of the catalogue. Calls go to POST /api/ai/actions/invoke and run the very tool definitions the embedded host registers, as the account that holds the token, in the project you name.

Use

// nikcli config
{ "plugin": [["file:///path/to/packages/nikcli-plugin/src/index.ts", { "url": "http://127.0.0.1:43111", "token": "<launch token>", "projectId": "<project id>" }]] }

or CADCAMFUN_URL, CADCAMFUN_TOKEN and CADCAMFUN_PROJECT in the environment. Create the token in the application (Settings → AI → Standalone nikcli): it is for the open project, read-only or read-write, opens only the action bridge, expires, and can be revoked there. (The application's own launch token also works and opens everything; prefer a scoped one.)

What it will not do

  • Delete or replace work (cad_edit delete, library_edit delete, vcs_edit restore, ...): in the application the host asks a person first, an outside client has no such prompt, and a confirm: true in the arguments is not an approval. The refusal says so.
  • Delegate to the specialist agents (agent): they run model sessions inside the application.
  • Go beyond its scope: a bridge token is for one project and, when read-only, reaches only read actions. The operator can narrow further with nikcli policy statements in <data dir>/ai/policy.json (bridge.use, tool.use).

Compatibility

test/compat.test.ts reads the shapes this package relies on (Plugin, PluginModule, Hooks.tool, tool()) from @nikcli-ai/plugin's declarations in the repo's .nikcli/ folder. apps/sidecar/test/nikcli-plugin.test.ts runs the plugin against the real sidecar routes.