AUVY

SDK compatibility

Node versions, peer dependencies, package entry points, and prior npm names.

SDK compatibility

Current packages (npm)

PackageMinimum Node
@auvy-os/client18+
@auvy-os/connect-client18+

Both ship ESM (.mjs) and CJS (.cjs) builds. "type": "module" projects should use default imports; CommonJS can require() the CJS artifacts.

Prior npm package names

Older releases and some examples may still reference @auvy-synapse/client and @auvy-synapse/connect-client. Treat them as aliases for the same surfaces documented on this site — prefer @auvy-os/* for new work.

Prior nameCurrent
@auvy-synapse/client@auvy-os/client
@auvy-synapse/connect-client@auvy-os/connect-client
@auvy-synapse/kernel (transitive)@auvy-os/kernel (transitive)

Peer dependencies

PackagePeersNotes
@auvy-os/client(none required)Standalone
@auvy-os/connect-client@auvy-os/client (optional)Required for browser transport; server subpath uses kernel only

Install both for browser Connect:

npm install @auvy-os/client @auvy-os/connect-client

Entry points

Import pathBuild outputUse
@auvy-os/clientdist/index.mjsAUVY OS product API
@auvy-os/connect-clientdist/index.mjsconnectFromSession, public types
@auvy-os/connect-client/advanceddist/advanced.mjsFull IntegrationsClient
@auvy-os/connect-client/serverdist/server/index.mjsS2S execute
@auvy-os/connect-client/server/envdist/server/env.mjsURL/secret env helpers

Transitive kernel

@auvy-os/kernel is a dependency (not a peer) of both published SDK packages. Types and small isomorphic helpers resolve through kernel subpaths. Do not depend on kernel directly unless you need shared schemas outside the client facades.

Browser bundlers

  • Vite / Nuxt / Next: default ESM imports work
  • Set public env vars (NEXT_PUBLIC_*) for baseUrl and publishable keys
  • Never embed API keys or Connect internal secrets in frontend bundles

Version alignment

Keep @auvy-os/client and @auvy-os/connect-client on the same minor release when using both in one app (e.g. 0.6.x).

On this page