Resolves: RHEL-111635
Extend existing shebang fixes to cover all npm nested modules and
shell scripts that call 'node' as a command. This prevents failures
when scripts try to call /usr/bin/node which is not shipped, instead
redirecting them to the versioned /usr/bin/node-22 binary.
Fixes include:
- All JavaScript/TypeScript files with node shebangs in npm nested modules
- Shell scripts like node-gyp that call 'node' as a command
Until now, the nodejs_abi dependency generator has lived in
nodejs-packaging. However, it depends on (an uses only) /usr/bin/node,
thus only working and being accurate for the default stream.
Moving the generator into a specific stream and modifying it to use
the versioned binary should ensure that it is valid for whatever stream
is used for compiling the binary extension in question.
Related: RHEL-67814
Signed-off-by: Jan Staněk <jstanek@redhat.com>
Obsoleting the versioned rpms without bounds
prevents the distribution to ever switch back to versioned rpms if desired.
Adding an upper bound is the first step of doing that switch.
Related: RHEL-67814
There is a new (?) script deps/npm/bin/npm-prefix.js
with the /usr/bin/env hashbang left intact,
which caused npm to always pull in whatever nodejs was currently
the default one.
Now all the scripts there should have the hashbangs adapted to our
naming and no new nodes pulled by installing npm.
Signed-off-by: Jan Staněk <jstanek@redhat.com>
Related: RHEL-76035
