We’re utilizing NPM for our package management and have decided to include the node_modules directory in our version control to prevent build server reliance on external resources. Recently, we’ve integrated Sass, which requires node-sass, and this in turn needs a complied libsass version. When executing npm install node-sass, NPM fetches binaries suitable for the corresponding OS and CPU. Our situation is challenging since our development setups are x64 while the build server operates on x32 architecture, leading to compatibility issues with the x64 node-sass binaries. Is there a method to instruct npm to retrieve bindings that cater to different architectures?
One trick that might work is using postinstall scripts to conditionally build or fetch binaries based on the target architecture. You could check process.arch during the install process and run specific commands. It’s not perfect but might save u the hassle of manual edits. Worth a look!
Another possible solution is to leverage the npm ci command, especially designed for continuous integration environments. This command installs packages based on the exact versions recorded in your package-lock.json file. If you pre-build or pre-fetch the required binaries for each architecture and commit the correct package-lock.json, the build server should be able to handle dependencies without issues. Also, check if platform-specific prebuilt binaries are available in the npm repository; this can minimize manual handling of different architectures.