Migrate native addon from nan to node-addon-api (N-API)

[sebi2k1]

Summary

• Replace nan with node-addon-api in both native source files (can.cc, signals.cc) and the build configuration (binding.gyp)
• node-addon-api wraps the stable N-API layer, guaranteeing ABI compatibility across Node.js major versions — a binary compiled once for Node.js 20 continues to load on Node.js 22 and 24 without recompilation
• Adds Dockerfile.build-test for reproducing the Linux build locally

Motivation

Users who upgrade Node.js (e.g. from v20 to v22) currently find the native addon silently broken until they manually rebuild. This is a common pain point for ioBroker adapters and other downstream consumers. N-API eliminates the need to recompile on major version upgrades and makes prebuilt binaries (e.g. via prebuildify) feasible in the future.

What changed

File	Change
package.json	nan → node-addon-api ^8.0.0
binding.gyp	Updated include path expression; added NAPI_DISABLE_CPP_EXCEPTIONS
native/can.cc	Nan::ObjectWrap → Napi::ObjectWrap<T>; static methods → instance methods; Nan::Persistent → Napi::FunctionReference/ObjectReference; napi_env stored for uv_async callbacks
native/signals.cc	NAN_METHOD → Napi::Value free functions; all Nan::* replaced with Napi::*
Dockerfile.build-test	New — builds the package on node:22-bookworm-slim for verification

Test plan

• Compiled cleanly on Node.js 22 / Linux arm64 (Debian bookworm) — zero warnings
• Verify npm test passes on a machine with a real or virtual CAN interface (vcan0)
• Smoke-test: load the binary built on Node.js 20 under Node.js 22 without rebuilding

🤖 Generated with Claude Code

[MyHomeMyData]

Thank you for implementing this so quickly — that's much appreciated!

Tested on Node.js 22.22.3 / Linux x64. The native addon builds and loads correctly — ABI stability works as expected.

However, npm run build:ts fails because the declared devDependency typescript@4.8.4 is incompatible with the tsconfig base @tsconfig/node22, which requires TypeScript ≥ 5.4 for the es2024, ESNext.Collection and ESNext.Iterator lib targets.

Additionally, tsc inadvertently picks up .js files from the parent project directory (4 levels above the package). Adding an explicit include or rootDir to tsconfig.json would prevent this.

As a result, dist/socketcan.js is missing after install and the package cannot be loaded. Could you update the TypeScript devDependency and add a prepare script (or include dist/ in the repository) so the package is usable out of the box?

[sebi2k1]

Thank you for implementing this so quickly — that's much appreciated!

Tested on Node.js 22.22.3 / Linux x64. The native addon builds and loads correctly — ABI stability works as expected.

However, npm run build:ts fails because the declared devDependency typescript@4.8.4 is incompatible with the tsconfig base @tsconfig/node22, which requires TypeScript ≥ 5.4 for the es2024, ESNext.Collection and ESNext.Iterator lib targets.

Additionally, tsc inadvertently picks up .js files from the parent project directory (4 levels above the package). Adding an explicit include or rootDir to tsconfig.json would prevent this.

As a result, dist/socketcan.js is missing after install and the package cannot be loaded. Could you update the TypeScript devDependency and add a prepare script (or include dist/ in the repository) so the package is usable out of the box?

Fixed now and also dropped support for the old EOL node version.