Open hekike opened 6 years ago
Is there a described mechanism for building a single protobuf library out of the numerous type files that get generated with the new option? While specifying the various options the closure compiler gets hung up on jspb
built-in functions, even though I provide the google-protobuf library as a dependency.
Really what is required, is for the compiler to spit a single file that doesn't have global pollution. Any hints, on dealing with protobuf specific dependencies greatly appreciated.
The
google-protobuf
npm library pollutes the global scope through theglobal.proto
variable. This pollution causes conflict between different versions ofgoogle-protobuf
in the samenode
process as they overwrites each other.Reproduce:
google-protobuf@3.3.0
as a dependencygoogle-protobuf@3.1.0
as a dependencyIf dependency B is required after A, the older version of
google-protobuf
owervrites the new versionsglobal.proto
in the process.