fix(core): load the native addon on every Node major

[not-matthias]

Ship a single Node-API prebuild for the native core, so one binary covers both supported Node majors instead of one binary per ABI.

Since c5c63ca the addon has shipped ABI-pinned prebuilds (node.abi127.node, node.abi137.node). node-gyp-build matches those on an exact process.versions.modules, so on any other major it finds no candidate, native_core silently falls back to the no-op stub, and every benchmark dies with Native core module is not bound, CodSpeed integration will not work properly. That contradicts what nodeVersion.ts already tells users, which is that other versions are experimental rather than fatal.

Only one V8 entry point stood in the way of a single prebuild. v8::String::Utf8Value's constructor gained a defaulted WriteOptions argument in Node 24, and WriteUtf8 gave way to WriteUtf8V2 in Node 26, so no single string-conversion symbol resolves across majors:

symbol	22	24	26
String::Utf8Value::Utf8Value(Isolate*, Local<Value>)	yes	no	yes
String::Utf8Length / String::WriteUtf8	yes	yes	no
String::WriteUtf8V2	no	yes	yes

Note the middle row: reverting to the pre-c591e88 formulation would satisfy 22 and 24 today, but it is the one that V8 has already removed, so it re-arms the same failure for the next bump. The other fourteen V8 symbols the perf-map handler needs (CodeEventHandler ctor/dtor/Enable/Disable, the eight CodeEvent getters, Isolate::GetCurrent) are present in every binary checked. So the conversion goes through Node-API, which is versioned and does not move.

Two packaging details worth attention during review:

• prebuildify 6 defaults --name to the package name and dropped the napi filename tag, contradicting its own README. A bare --napi emits @codspeed+core.node or node.node, both of which node-gyp-build@4.6.0 rejects (if (tags.abi !== abi && !tags.napi) return false). Hence the explicit --name node.napi.
• The target is pinned to 22.0.0 so we compile against the oldest supported headers rather than whatever node-abi currently believes is newest, which today is 26.

setupCore also now reports the underlying require failure plus the Node version, ABI and platform. Previously it went to logDebug, which is why the original report gave nothing to work from.

Why CI did not catch this

The node-versions job runs pnpm turbo run build, which includes build-native-addon, under the same Node it then benchmarks with. The addon is always compiled for the running ABI, so an incompatible prebuild is structurally unobservable there. The new native-abi job builds one prebuild set and loads it from Node 22 and 24, calling setupCore because the symbols bind lazily: a broken addon passes a bare require and only dies once LinuxPerf::Start runs.

Verified locally against both failure modes on a from-scratch build:

• ABI-pinned prebuild for 22 only: Node 24 exits 1 with the new diagnostic naming the missing ABI.
• --napi with the old Utf8Value call: Node 24 exits 127 on undefined symbol: _ZN2v86String9Utf8ValueC1EPNS_7IsolateENS_5LocalINS_5ValueEEE, while 22 passes.
• With the fix, one artifact passes on 22 and 24.

Scope

Both designs satisfy the 22 and 24 requirement, so the argument for this one is what happens outside it: users on another major degrade with the existing experimental-version warning instead of hitting an unreadable stub failure, and the package ships three prebuilt binaries instead of six. The tradeoff is that the two supported majors now share one binary and therefore depend on those fourteen V8 symbols staying put, rather than each being compiled against its own headers. That is the same bet the v5 line ran successfully for three years, and the new job fails loudly if it ever stops holding.

This does not remove the V8 C++ dependency. Retiring it entirely means dropping LinuxPerf for --perf-basic-prof, which the walltime path already uses and which writes the same /tmp/perf-<pid>.map.

[codspeed-hq]

Merging this PR will regress 1 benchmark

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 5 improved benchmarks
❌ 1 regressed benchmark
✅ 232 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Memory	switch 2	432 B	656 B	-34.15%
⚡	Simulation	recursive fibo 10	1,371.7 µs	298.5 µs	×4.6
⚡	WallTime	test_iterative_fibo_10	120 ns	96 ns	+25%
⚡	WallTime	switch 1	84 ns	72 ns	+16.67%
⚡	WallTime	test sync baz 10	108 ns	96 ns	+12.5%
⚡	WallTime	short body	2.1 µs	1.9 µs	+10.06%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing fix/napi-prebuilds (9f111ed) with main (9338d9a)}

[greptile-apps]

Greptile Summary

This PR replaces ABI-specific native-addon builds with one Node-API-tagged prebuild and adds Node 22/24 compatibility validation and richer binding diagnostics.

• Converts V8 strings through Node-API to avoid moving V8 string-conversion symbols.
• Packages one prebuild compiled against Node 22 headers.
• Adds a CI job that loads and exercises the same addon under Node 22 and Node 24.
• Preserves native binding errors and includes runtime details in setup failures.

Confidence Score: 4/5

The native string conversion must be fixed before merging because routine V8 code events can cause an out-of-bounds native write.

The new Node-API conversion allocates storage for the UTF-8 payload but tells Node-API that an additional terminator byte is writable, exposing benchmark processes to memory corruption while perf-map names are generated.

Files Needing Attention: packages/core/src/native_core/linux_perf/utils.h

Important Files Changed

Filename	Overview
packages/core/src/native_core/linux_perf/utils.h	Replaces unstable V8 conversion symbols with Node-API, but supplies a destination size one byte larger than the allocated string storage.
packages/core/src/native_core/linux_perf/linux_perf_listener.cc	Threads the Node-API environment into function and script-name conversion; its live code-event paths expose the conversion overflow.
packages/core/package.json	Changes native packaging to a single explicitly named N-API prebuild compiled against Node 22 headers.
.github/workflows/ci.yml	Adds a focused Linux job that builds one native artifact and exercises it under both supported Node majors.
scripts/assert-native-binding.cjs	Exercises lazy native symbol binding and verifies that Linux perf produces map entries.
packages/core/src/index.ts	Improves native-binding failure diagnostics with the underlying error and runtime ABI/platform details.

Sequence Diagram

sequenceDiagram
    participant CI as Native ABI CI
    participant Build as prebuildify
    participant Loader as node-gyp-build
    participant Core as setupCore
    participant Perf as LinuxPerf
    participant NAPI as Node-API
    CI->>Build: Build node.napi.node against Node 22
    loop Node 22 and Node 24
        CI->>Loader: Load shared prebuild
        Loader->>Core: Bind native_core
        Core->>Perf: Start code-event handler
        Perf->>NAPI: Convert V8 names to UTF-8
        Core->>Perf: Stop handler
    end

Loading

Prompt To Fix All With AI

### Issue 1
packages/core/src/native_core/linux_perf/utils.h:25-29
**UTF-8 conversion overruns buffer**

When a V8 code event has a nonempty function or script name, this allocates `length` writable characters but tells `napi_get_value_string_utf8` that `length + 1` bytes are available, causing the trailing NUL to be written beyond the string's guaranteed storage and potentially crashing or corrupting the benchmark process.

```suggestion
  std::string result(length + 1, '\0');
  if (napi_get_value_string_utf8(env, value, result.data(), result.size(),
                                 &length) != napi_ok) {
    return std::string();
  }
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "ci: check the prebuilt addon binds on ev..." | Re-trigger Greptile}