fix: disable wasm highlighter on riscv64

riscv64 with sv39 has limited virtual memory space, where creating
too many (>=20) wasm memory instances fails.
See nodejs/node#60591 for more details.

This PR fixes the following error encountered during `make test-only`
on riscv64:

    [07:02:55.797] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance
    RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instancemake[1]: *** [Makefile:392: test/addons/.docbuildstamp] Error 1
    make: *** [Makefile:352: test-only] Error 2

Signed-off-by: Levi Zim <[email protected]>

Author: kxxt

src/utils/highlighter.mjs

@@ -39,7 +39,11 @@ function isCodeBlock(node) {
 export const highlighter = await createHighlighter({
   // s390x machines throw memory issues on WASM builds
   // https://github.com/nodejs/node/blob/c9acf345922bd758fbb3f16ee6256aa165260219/test/common/sea.js#L55
-  wasm: process.arch !== 's390x',
+  //
+  // riscv64 with sv39 has limited virtual memory space, where creating
+  // too many (>20) wasm memory instances fails.
+  // https://github.com/nodejs/node/pull/60591
+  wasm: !['riscv64', 's390x'].includes(process.arch),
 });
 
 /**