Releases: BYVoid/rules_node_addon
Releases Β· BYVoid/rules_node_addon
Release list
v1.0.3
Full Changelog: v1.0.2...v1.0.3
node_addonnow setsallow_symlink = Falseon the finalcopy_filestep that produces the.nodeoutput. This makes the generated addon a real.nodefile rather than a symlink.- The reason is that some Node.js import/loading paths resolve a symlink before loading the addon. When that happens, Node can end up loading the original platform shared library path (
.so/.dylib) instead of the intended.nodepath, which can cause addon loading to fail. Copying the file avoids that path/extension mismatch. - The full TypeScript example was updated to consume the addon output directly instead of copying it into
dist/, and its now-unused directbazel_skylibdependency was removed. The example test resolvesADDON_PATHrelative to the test file so both the JS and Bun test entry points still load the same addon reliably.