{"error": {"canonicalCode": "INVALID_ARGUMENT", google cloud

Question

Got this error while deploying cloud functions with node version: Node.js 8 (Beta)

Build failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "npm_install had stderr output:\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/typedarray-83fafd37/.travis.yml'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-c4f762ab/lib/_stream_transform.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-840f6280/lib/_stream_transform.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-c4f762ab/lib/_stream_writable.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-d7e024ba/lib/_stream_transform.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-840f6280/lib/_stream_writable.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/readable-stream-d7e024ba/lib/_stream_writable.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/protobufjs-e78f053b/dist/protobuf.min.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/jimp-a023a0b7/browser/examples/test.html'\nnpm WARN tar ENOENT: no such file or directory, lstat '/workspace/node_modules/.staging/jimp-a023a0b7/browser/lib'\nnpm WARN tar ENOENT: no such file or directory, lstat '/workspace/node_modules/.staging/jimp-a023a0b7/browser/lib'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/ajv-95df8818/dist/ajv.min.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/jimp-a023a0b7/browser/README.md'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/@firebase/database-9dc4a163/dist/index.d.ts'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/@firebase/database-9dc4a163/dist/index.esm.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/moment-45f2522a/min/moment-with-locales.min.js'\nnpm WARN tar ENOENT: no such file or directory, open '/workspace/node_modules/.staging/googleapis-329f5f2f/build/src/apis/bigquery/v2.js'\nnpm ERR! code E404\nnpm ERR! 404 Not Found: [email protected]\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /builder/home/.npm/_logs/2019-01-10T13_28_58_185Z-debug.log\n\nerror: npm_install returned code: 1", "errorType": "InternalError", "errorId": "C5E68EBB"}}

Answer 1

The problem is solved by removing "package-lock.json" file.