This repository has been archived by the owner on Oct 17, 2023. It is now read-only.
ENOENT: no such file or directory, open 'operations.json' #663
Labels
api: translate
Issues related to the googleapis/nodejs-translate API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
The new version of nodejs-translate resolve the problem with
ENOENT: no such file or directory, open '/protos/protos.json
requested googleapis/nodejs-pubsub#1246 but right now there is a new problemENOENT: no such file or directory, open 'operations.json'
Information about my environment:
"@google-cloud/translate": "^6.2.1"
used as dependencies on Lambda (AWS)Version of node :
Node.js 10.x
Application has been written in TypeScript.
Full output of stack:
"stack": "Error: ENOENT: no such file or directory, open 'operations.json'\n at Object.openSync (fs.js:443:3)\n at Object.readFileSync (fs.js:343:35)\n at fetch (/var/task/app.js:99576:34)\n at Root.load (/var/task/app.js:99610:13)\n at Root.loadSync (/var/task/app.js:99651:17)\n at Object.loadProtosWithOptionsSync (/var/task/app.js:199897:29)\n at Object.loadSync (/var/task/app.js:195232:31)\n at GrpcClient.loadFromProto (/var/task/app.js:97086:48)\n at GrpcClient.loadProto (/var/task/app.js:97117:21)\n at new OperationsClientBuilder (/var/task/app.js:100198:40)"
The text was updated successfully, but these errors were encountered: