Each generated package in google-cloud-node includes a protos/ folder containing raw .proto source files, compiled JavaScript/TypeScript wrappers, and a JSON representation.
For example, packages/google-cloud-secretmanager/protos/ contains:
google/cloud/secretmanager/v1/resources.protogoogle/cloud/secretmanager/v1/service.protogoogle/cloud/secrets/v1beta1/resources.protogoogle/cloud/secrets/v1beta1/service.protoprotos.d.tsprotos.jsprotos.json
The raw .proto files under protos/google/ seem to only be used at build time by compileProtos, which reads paths from *_proto_list.json files and compiles them into protos.json, protos.js, and protos.d.ts. At runtime, the client libraries only import the compiled artifacts.
The raw .proto files are never read from disk. We should remove the protos/ folders from the published npm packages, as a prerequisite to onboarding Node.js to librarian.
Each generated package in google-cloud-node includes a
protos/folder containing raw.protosource files, compiled JavaScript/TypeScript wrappers, and a JSON representation.For example,
packages/google-cloud-secretmanager/protos/contains:google/cloud/secretmanager/v1/resources.protogoogle/cloud/secretmanager/v1/service.protogoogle/cloud/secrets/v1beta1/resources.protogoogle/cloud/secrets/v1beta1/service.protoprotos.d.tsprotos.jsprotos.jsonThe raw
.protofiles underprotos/google/seem to only be used at build time bycompileProtos, which reads paths from*_proto_list.jsonfiles and compiles them intoprotos.json,protos.js, andprotos.d.ts. At runtime, the client libraries only import the compiled artifacts.The raw
.protofiles are never read from disk. We should remove theprotos/folders from the published npm packages, as a prerequisite to onboarding Node.js to librarian.