Open jansu76 opened 9 months ago
In it's current state I don't think there's a solution, I'm currently doing a refactor related to the configurable components in this plugin and will tackle this as part of that
If all your linux systems use musl and you have the ability to setup an internal mirror I guess there's technically a workaround available by repackaging it
there's technically a workaround available by repackaging it
To make sure I understand, do you mean taking an unofficial build, and changing it so that the binary is in node-v18.16.1-linux-x64/bin/node
instead of node-v18.16.1-linux-x64-musl/bin/node
?
Yeah, it's not a pretty solution though and could easily lead to some confusion
I want to use gradle-node-plugin to install node on alpine linux. Using this advice https://github.com/node-gradle/gradle-node-plugin/issues/51#issuecomment-623097695 combined with this https://github.com/node-gradle/gradle-node-plugin/blob/main/docs/faq.md#is-this-plugin-compatible-with-centralized-repositories-declaration I managed to get a working configuration that downloads the correct binary package from https://unofficial-builds.nodejs.org/download/release/v18.16.1/node-v18.16.1-linux-x64-musl.tar.gz
build.gradle:
settings.gradle
However, npmInstall fails since it tries to look for the binary in the wrong directory. Can I do something to fix this?
Binary is in
node-v18.16.1-linux-x64-musl
, not innode-v18.16.1-linux-x64
.