| Crates.io | autonomi-nodejs |
| lib.rs | autonomi-nodejs |
| version | 0.1.1 |
| created_at | 2025-04-22 22:07:59.586324+00 |
| updated_at | 2025-06-26 20:29:55.999378+00 |
| description | NodeJS bindings for the autonomi client |
| homepage | |
| repository | |
| max_upload_size | |
| id | 1644720 |
| size | 3,148,885 |
The client API for Autonomi. This Node.js addon provides bindings into the Rust autonomi crate.
Add the @withautonomi/autonomi package to your project. For example, using npm:
$ npm install @withautonomi/autonomi
Using a modern version of Node.js we can use import and async easily when we use the .mjs extension. Import the Client and you're ready to connect to the network!
// main.mjs
import { Client } from '@withautonomi/autonomi'
const client = await Client.initLocal()
Run the script:
$ node main.js
Work in progress:
For general guides and usage, see the Developer Documentation. This is currently worked on specifically to include Node.js usage.
For example usage, see the __test__ directory. Replace import { .. } from '../index.js' to import from @withautonomi/autonomi instead.
To contribute or develop on the source code directly, we need a few requirements.
npm install --global yarnyarn global add @napi-rs/cliInstall the dependencies for the project:
$ yarn install
Then build using the napi CLI:
$ npx napi build
Run the test script:
yarn test
# Or run a specific test
yarn test __test__/register.spec.mjs -m 'registers errors'
Before publishing, bump the versions of all packages with the following:
$ npm version patch --no-git-tag-version
Use major or minor instead of patch depending on the release.
It's a good practice to have an unreleased version number ready to go. So if 0.4.0 is the version released on NPM currently, package.json should be at 0.4.1.
Use the 'JS publish to NPM' workflow (nodejs-publish.yml) to publish the package from main or a tag. This workflow has to be manually dispatched through GitHub.