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

@trycua/fleet

v0.1.2

Published

Browser and WebAssembly SDK for Cua Fleet sandbox lifecycle management

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dillon808dillon808f-trycuaf-trycuamdean808mdean808

Keywords

computer-usesandboxagentsfleetorchestrationautomation

Readme

@trycua/fleet

Browser and Node.js WebAssembly bindings for the Cua Fleet control plane. Both entry points expose the generated lifecycle client used to create templates, pools, claims, and authenticated requests to sandbox services.

The package is built from the public Fleet mirror in libs/fleet. That mirror is synchronized from the canonical Fleet repository, so the npm release and public SDK source share one repository and release history.

Install

npm install @trycua/fleet

Browser

import {
  CyclopsClient,
  CyclopsTokenProviderConfigurationBuilder,
  uniffiInitAsync,
} from '@trycua/fleet/browser';

await uniffiInitAsync();
const configuration = new CyclopsTokenProviderConfigurationBuilder()
  .baseUrl('https://run.cua.ai')
  .poolPollIntervalMs(5_000n)
  .poolPollLimit(120)
  .claimPollIntervalMs(5_000n)
  .claimPollLimit(120)
  .build();
const client = CyclopsClient.connectBrowserWithAccessToken(configuration, accessToken);

Node.js

The Node entry loads the same WASM artifact from disk and supplies a fetch-based UniFFI HTTP transport, so it does not require a platform-specific native libcyclops_sdk.

import { CyclopsTokenProviderConfigurationBuilder, createFleetClient } from '@trycua/fleet/node';

const configuration = new CyclopsTokenProviderConfigurationBuilder()
  .baseUrl('https://run.cua.ai')
  .poolPollIntervalMs(5_000n)
  .poolPollLimit(120)
  .claimPollIntervalMs(5_000n)
  .claimPollLimit(120)
  .build();
const client = await createFleetClient(configuration, accessToken);

The package root uses conditional exports: browser-aware bundlers receive the browser entry and Node.js receives the Node entry. Explicit subpath imports are recommended for application code and tests.

Development

pnpm --dir libs/typescript/fleet build
pnpm --dir libs/typescript/fleet pack:check

The build regenerates the browser UniFFI binding from libs/fleet, compiles the pinned Rust SDK to WebAssembly, and emits both ESM entry points plus TypeScript declarations.

Links