Test node binding

Skill NVIDIA/NeMo-Relay/.agents/skills/test-node-binding

Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checksFrom its SKILL.md

Install

npx -y skills add NVIDIA/NeMo-Relay --skill test-node-binding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, as published. Nobody here has run it

Build And Test Node Binding

Companion Guidance

Use karpathy-guidelines alongside this skill for implementation or review work. Keep changes scoped, surface assumptions, and define focused validation before editing.

Use this skill when the change is primarily in crates/node, the generated Node surface, or Node-facing examples/docs.

Default Path

Format changed Node files with npm run format --workspace=nemo-relay-node.
Install dependencies and build with just build-node when you need to validate packaging/build output.
Run just test-node for the normal dev/test loop.
If any Rust files changed as part of the Node work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings.
Use just ci=true test-node when you want the CI-style coverage and JUnit path.

Common Commands

# Explicit release build
just build-node

# Format Node files
npm run format --workspace=nemo-relay-node

# Standard test loop
just test-node

# Required when the Node change also touched Rust code
cargo fmt --all
just test-rust
cargo clippy --workspace --all-targets -- -D warnings

# CI-style coverage and JUnit test loop
just ci=true test-node

Useful Extras

# Public API docstring checks when surface docs changed
npm run check:docstrings --workspace=nemo-relay-node

When To Escalate

If the change touched crates/core, crates/adaptive, or the generated Rust binding layer under crates/node/src, also use validate-change.
If the change is just documentation around Node usage, keep validation targeted.

References

package.json
package-lock.json
crates/node/package.json
docs/getting-started/nodejs.md
README.md
docs/contribute/testing-and-docs.md
validate-change