prebuild assets location resolution at runtime

[longlho]

Question about an existing feature

What are you trying to achieve?

I'm trying to integrate sharp in our bazel build which is hermetic and uses sandbox for everything. Effectively what I'm looking for is:

• Download libvips to a specific location (sandboxed)
• Download sharp bindings to a specific location (sandboxed)
• Ability to tell sharp to resolve bindings + libvips from those 2 locations at runtime.

Is there a way to do that?

When you searched for similar issues, what did you find that might be related?

#3270
#2741

Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question

Please provide sample image(s) that help explain this question

[lovell]

Hi, did you see https://sharp.pixelplumbing.com/install#custom-prebuilt-binaries ?

[longlho]

Yup I did but my understanding is i have to set them during "npm install" and not after?

[lovell]

Would symlinks suffice? You'd need to link the node_modules/sharp/build and node_modules/sharp/vendor directories to the decompressed contents of their respective tarballs.

[longlho]

Unfortunately no because the build sandbox is readonly :(

[lovell]

Have you considered installing libvips from package manager (or from source)?

[longlho]

Yup I've kinda tried but bazel manages all external dependencies and is very explicit (e.g download this file from this host with this checksum) and trying to re-compile is pretty hard. I also cannot install it to a global location because it's non-hermetic. Or maybe I'm misunderstanding your suggestion?

[lovell]

Did you see the example provided by Bazel at https://github.com/bazelbuild/rules_nodejs/tree/stable/e2e/nodejs_image ?

[longlho]

Yup pulling in Docker is definitely an option I was just wondering if it can be done w/o it :) I'd love to understand the complexity of making those deps runtime as well.

[lovell]

There's another example at https://github.com/aspect-build/rules_js/tree/main/e2e/npm_link_package if you hadn't seen it.

[longlho]

Yup rules_js is in beta and requires a decent LOE to migrate. It's in our roadmap but at least not until it's stabler.

[lovell]

@longlho Were you able to make any progress with this?

[lovell]

Closing due to inactivity but please feel free to reopen with more details if further help is required.

In summary, from what I've seen, https://github.com/aspect-build/rules_js offers the best approach, and even uses sharp as an example in its tests.

[fmnxl]

Just documenting this in case someone is having the same issue on Nix, since like Bazel it also works with a strict sandbox. I'm building a Next.js app which is packaged with Nix's buildNpmPackage.

Include nativeBuildInputs = [ pkgs.pkg-config ]; buildInputs = [ pkgs.vips ]; in your builder of choice, it would make a global (as far as the build phase is concerned) installation of libvips available. I'm using pkgs.buildNpmPackage, so my config is:

pkgs.buildNpmPackage rec {
  pname = "my-project";
  version = "0.0.1";

  src = pkgs.lib.cleanSource ./.;

  npmDepsHash = "some hash";
  npmPackFlags = [ "--ignore-scripts" ];

  nativeBuildInputs = [
    pkgs.python3 # needed by buildNpmPackage
    pkgs.pkg-config
  ];
  buildInputs = [
    pkgs.vips
  ];
  PKG_CONFIG_PATH = pkgs.pkg-config;
}

[lovell]

Anyone interested in sandboxed builds should probably subscribe to #3750 for updates.