Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@bufbuild/protoc-gen-es) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@bufbuild/protoc-gen-es
The code generator for Protocol Buffers for ECMAScript. For example, the following definition:
message Person {
string name = 1;
int32 id = 2; // Unique ID number for this person.
string email = 3;
}Is compiled to an ECMAScript class that can be used like this:
let pete = new Person({
name: "pete",
id: 123
});
let bytes = pete.toBinary();
pete = Person.fromBinary(bytes);
pete = Person.fromJsonString('{"name": "pete", "id": 123}');Learn more about the project at github.com/bufbuild/protobuf-es.
Installation
protoc-gen-es is a code generator plugin for Protocol Buffer compilers,
like buf and protoc.
It generates base types - messages and enumerations - from your Protocol Buffer
schema. The generated code requires the runtime library @bufbuild/protobuf.
To install the plugin and the runtime library, run:
npm install --save-dev @bufbuild/protoc-gen-es
npm install @bufbuild/protobufWe use peer dependencies to ensure that code generator and runtime library are compatible with each other. Note that yarn and pnpm only emit a warning in this case.
Generating code
With buf
Add a new configuration file buf.gen.yaml:
# buf.gen.yaml defines a local generation template.
# For details, see https://docs.buf.build/configuration/v1/buf-gen-yaml
version: v1
plugins:
# This will invoke protoc-gen-es and write output to src/gen
- name: es
out: src/gen
opt: target=tsAdd the following script to your package.json:
{
"name": "your-package",
"version": "1.0.0",
"scripts": {
"generate": "buf generate"
},
// ...
}To generate code for all protobuf files within your project, simply run:
npm run generateNote that buf can generate from various inputs,
not just local protobuf files.
With protoc
PATH=$PATH:$(pwd)/node_modules/.bin \
protoc -I . \
--es_out src/gen \
--es_opt target=ts \
a.proto b.proto c.protoNote that we are adding node_modules/.bin to the $PATH, so that the protocol
buffer compiler can find them. This happens automatically with npm scripts.
Since yarn v2 and above does not use a node_modules directory, you need to
change the variable a bit:
PATH=$(dirname $(yarn bin protoc-gen-es)):$PATHPlugin options
target
This option controls whether the plugin generates JavaScript, TypeScript, or TypeScript declaration files.
Possible values:
target=js- generates a_pb.jsfile for every.protoinput file.target=ts- generates a_pb.tsfile for every.protoinput file.target=dts- generates a_pb.d.tsfile for every.protoinput file.
Multiple values can be given by separating them with +, for example
target=js+dts.
By default, we generate JavaScript and TypeScript declaration files, which
produces the smallest code size. If you prefer to generate TypeScript, use
target=ts.
keep_empty_files=true
By default, protoc-gen-es (and all other plugins based on @bufbuild/protoplugin) omit empty files from the plugin output. This option disables pruning of empty files, to allow for smooth interoperation with Bazel and similar tooling that requires all output files to be declared ahead of time. Unless you use Bazel, it is very unlikely that you need this option.