Prebuild name has changed in v6

[kirrg001]

Hi!

We wanted to update from v5 to v6, but I have noticed that the name of the prebuild has changed.

7b6dcbd

The output is now:

prebuilds/linux-arm/@PKG-NAME.armv6.node

We are supporting various Node.js prebuilds versions. Could you please explain how this will work? Is there a migration guide from v5 to v6?

-rwxr-xr-x 1 kirrg001kirrg001 staff 17992 7 Mai 10:09 PKG-NAME.armv6.node
-rwxr-xr-x 1 kirrg001kirrg001 staff 17992 15 Aug 2024 node.abi108.armv6.node
-rwxr-xr-x 1 kirrg001kirrg001 staff 18000 15 Aug 2024 node.abi108.armv7.node
-rwxr-xr-x 1 kirrg001kirrg001 staff 17988 15 Aug 2024 node.abi115.armv6.node

Thanks

[mafintosh]

just wants the package name in there. you dont need to add multiple version of prebuilds to your module, the module itself defines the the version to load the prebuild so just support latest.

[kirrg001]

the module itself defines the the version to load the prebuild so just support latest.

I can't follow this statement. We ship a module, which supports Node v18 - Node v24 in each released version. How can we only ship one latest prebuild?

[matthewh]

I also encountered this issue running prebuildify v6. I was not able to make a single package with support for node 18-24 because setting the target(s) overwrote the same file each time. prebuildify v5 does not have this issue.

[vweevers]

If you use Node-API (and you should) then you only need a single prebuild because Node-API provides forward-compatibility (i.e. it'll work on the current Node.js version and every future version). Node-API is enabled by default in prebuildify 6.

You can technically disable it with --no-napi but I'm not sure if we intend to keep supporting that (@mafintosh?).