napi-rs-bindings

napi-rs conventions for exposing a Rust core to Node.js: #[napi] macros, napi::Error mapping, auto-generated .d.ts types, async Promises, and CommonJS/ESM output. Load when generating or reviewing nap

SKILL.md

GitHub
  • Use #[napi] macro for Node.js-visible functions and classes. Use #[napi(constructor)] for constructors.
  • Map Rust errors to JavaScript Error objects via napi::Error. Return Result<T> from all fallible functions.
  • Use napi::bindgen_prelude::* for common type conversions. Use Buffer for binary data.
  • Support both CommonJS and ESM output. Generate .d.ts type definitions automatically.
  • Use #[napi(ts_return_type = "...")] for complex TypeScript types the macro can't infer.
  • Build with napi build --release. Test from TypeScript/JavaScript using a JS test runner (e.g., Vitest or Jest).
  • Async: use #[napi] on async fn for Promise-returning functions. Use AsyncTask for CPU-bound work.
  • Keep Node.js wrappers thin — business logic in Rust, JS provides idiomatic API.
  • Handle BigInt, Date, and other JS-specific types explicitly.
  • Anti-patterns: no panics in napi functions, no blocking the event loop, no manual JsValue manipulation.

Related in testing

frontend-testing-langgenius-dify

Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, s...

by langgenius
127,079

skill-creator-langgenius-dify

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an exist...

by langgenius
127,079

browser-use-browser-use-browser-use

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs...

by browser-use
76,633