Skip to content
This repository was archived by the owner on Sep 10, 2026. It is now read-only.

Some libraries fail to install if node is not present on the PATH #40

Closed

Description

@rohanag12

I am trying to build a simple node app in an environment without NodeJS installed.

bazel build foo/src:bar_node_module

Most of the dependencies get installed successfully, but one package (chromedriver) fails with this error:

error /home/ubuntu/.cache/bazel/_bazel_ubuntu/9a9b3273327e7f32d450222011289241/external/bar-module-deps/node_modules/chromedriver: Command failed.
Exit code: 127
Command: node install.js
Arguments: 
Directory: /home/ubuntu/.cache/bazel/_bazel_ubuntu/9a9b3273327e7f32d450222011289241/external/bar-module-deps/node_modules/chromedriver
Output:
/bin/sh: 1: node: not found
 and referenced by '//foo/src:bar_node_module'

I believe the issue is in chromedriver's package.json file:

...
"scripts": {
    "install": "node install.js"
  }, ...

Since node is not present on the path, this step fails. Is there any way to get around this?

Activity

  1. pcj commented on Oct 17, 2017

    @pcj
    Contributor

    Think I have a fix for this in a larger PR that will prepend the node dir to $PATH in the launcher script. I hope to have that up by tonight.

  2. pcj commented on Oct 27, 2017

    @pcj
    Contributor

    Should be fixed with #41. Pls re-open if this remains an issue @rohanag12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions