Skip to content

resolveCLIBinary: abstract-cli could not be accessed at the expected path: [] #304

Open
@Rulevoid

Description

@Rulevoid

I'm using Azure Functions to run a nodejs function which consumes the abstract sdk. No issues running this locally, but consistently seeing issues with the resolveCLIBinary function throwing an error when trying to locate the cli. The path that the error spits out is correct and the cli binary is at that path. The deployed artifact has the node_modules directory at root as expected. This same issue was reported in Spectrum in May: https://spectrum.chat/abstract/developers/cant-access-abstract-cli-when-using-the-abstract-sdk-package~2ad41747-e801-4601-8bc2-852dbcb080c2

I have tried nodejs 10.x and 12.x both with the same issue.

Result: Failure Exception: Worker was unable to load function AbstractHook: 'Error: abstract-cli could not be accessed at the expected path: /home/site/wwwroot/node_modules/@elasticprojects/abstract-cli/bin/abstract-cli' Stack: Error: abstract-cli could not be accessed at the expected path: /home/site/wwwroot/node_modules/@elasticprojects/abstract-cli/bin/abstract-cli at resolveCLIBinary (/home/site/wwwroot/node_modules/@elasticprojects/abstract-cli/index.js:20:13) at Object.<anonymous> (/home/site/wwwroot/node_modules/@elasticprojects/abstract-cli/index.js:30:18) at Module._compile (internal/modules/cjs/loader.js:1138:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10) at Module.load (internal/modules/cjs/loader.js:986:32) at Function.Module._load (internal/modules/cjs/loader.js:879:14) at Module.require (internal/modules/cjs/loader.js:1026:19) at require (internal/modules/cjs/helpers.js:72:18) at Object.<anonymous> (/home/site/wwwroot/node_modules/abstract-sdk/dist/endpoints/Endpoint.js:96:15) at Module._compile (internal/modules/cjs/loader.js:1138:30)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions