Discussion

Version 12.1.0 of the Admin SDK added a dependency on a package called farmhash. This package has a dev dependency on python via node-gyp. The node-gyp package on older versions of Node looks for a binary called python. This results in npm install of the Admin SDK failing if it can't find a binary with that name ("env: python: No such file or directory").

Original error report: lovell/farmhash#47 (comment)

Fortunately, the owner of the farmhash package quickly added a prebuilt binary and released a version 3.3.1: lovell/farmhash#41

So, this PR updates the Admin SDK's package-lock.json to use farmhash version 3.3.1.

Folks can workaround this issue in the meantime by installing Python or aliasing an existing binary.

Testing

Steps to repro original issue:

1. Use Node version 14: nvm use 14
2. Perform a clean install: npm ci
3. Observe error "No prebuilt binaries found ... env: python: No such file or directory ... farmhash@3.3.0 install: prebuild-install || node-gyp rebuild"
4. Create Python virtual env named "venv" to define a local python binary: python3 -m venv ~/venv
5. Activate virtual env: source ~/venv/bin/activate
6. Repeat step 2
7. Observe no error

With this change:

1. Use Node version 14: nvm use 14
2. Perform a clean install: npm ci
3. Observe no error

API Changes

None