@evalops/maestro 0.10.18 → 0.10.21

package/node_modules/@bufbuild/protobuf/dist/cjs/wkt/gen/google/protobuf/compiler/plugin_pb.d.ts

@@ -1,490 +0,0 @@
-import type { GenEnum, GenFile, GenMessage } from "../../../../../codegenv2/types.js";
-import type { FileDescriptorProto, FileDescriptorProtoJson, GeneratedCodeInfo, GeneratedCodeInfoJson } from "../descriptor_pb.js";
-import type { Message } from "../../../../../types.js";
-/**
- * Describes the file google/protobuf/compiler/plugin.proto.
- */
-export declare const file_google_protobuf_compiler_plugin: GenFile;
-/**
- * The version number of protocol compiler.
- *
- * @generated from message google.protobuf.compiler.Version
- */
-export type Version = Message<"google.protobuf.compiler.Version"> & {
-    /**
-     * @generated from field: optional int32 major = 1;
-     */
-    major: number;
-    /**
-     * @generated from field: optional int32 minor = 2;
-     */
-    minor: number;
-    /**
-     * @generated from field: optional int32 patch = 3;
-     */
-    patch: number;
-    /**
-     * A suffix for alpha, beta or rc release, e.g., "alpha-1", "rc2". It should
-     * be empty for mainline stable releases.
-     *
-     * @generated from field: optional string suffix = 4;
-     */
-    suffix: string;
-};
-/**
- * The version number of protocol compiler.
- *
- * @generated from message google.protobuf.compiler.Version
- */
-export type VersionJson = {
-    /**
-     * @generated from field: optional int32 major = 1;
-     */
-    major?: number;
-    /**
-     * @generated from field: optional int32 minor = 2;
-     */
-    minor?: number;
-    /**
-     * @generated from field: optional int32 patch = 3;
-     */
-    patch?: number;
-    /**
-     * A suffix for alpha, beta or rc release, e.g., "alpha-1", "rc2". It should
-     * be empty for mainline stable releases.
-     *
-     * @generated from field: optional string suffix = 4;
-     */
-    suffix?: string;
-};
-/**
- * Describes the message google.protobuf.compiler.Version.
- * Use `create(VersionSchema)` to create a new message.
- */
-export declare const VersionSchema: GenMessage<Version, {
-    jsonType: VersionJson;
-}>;
-/**
- * An encoded CodeGeneratorRequest is written to the plugin's stdin.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorRequest
- */
-export type CodeGeneratorRequest = Message<"google.protobuf.compiler.CodeGeneratorRequest"> & {
-    /**
-     * The .proto files that were explicitly listed on the command-line.  The
-     * code generator should generate code only for these files.  Each file's
-     * descriptor will be included in proto_file, below.
-     *
-     * @generated from field: repeated string file_to_generate = 1;
-     */
-    fileToGenerate: string[];
-    /**
-     * The generator parameter passed on the command-line.
-     *
-     * @generated from field: optional string parameter = 2;
-     */
-    parameter: string;
-    /**
-     * FileDescriptorProtos for all files in files_to_generate and everything
-     * they import.  The files will appear in topological order, so each file
-     * appears before any file that imports it.
-     *
-     * Note: the files listed in files_to_generate will include runtime-retention
-     * options only, but all other files will include source-retention options.
-     * The source_file_descriptors field below is available in case you need
-     * source-retention options for files_to_generate.
-     *
-     * protoc guarantees that all proto_files will be written after
-     * the fields above, even though this is not technically guaranteed by the
-     * protobuf wire format.  This theoretically could allow a plugin to stream
-     * in the FileDescriptorProtos and handle them one by one rather than read
-     * the entire set into memory at once.  However, as of this writing, this
-     * is not similarly optimized on protoc's end -- it will store all fields in
-     * memory at once before sending them to the plugin.
-     *
-     * Type names of fields and extensions in the FileDescriptorProto are always
-     * fully qualified.
-     *
-     * @generated from field: repeated google.protobuf.FileDescriptorProto proto_file = 15;
-     */
-    protoFile: FileDescriptorProto[];
-    /**
-     * File descriptors with all options, including source-retention options.
-     * These descriptors are only provided for the files listed in
-     * files_to_generate.
-     *
-     * @generated from field: repeated google.protobuf.FileDescriptorProto source_file_descriptors = 17;
-     */
-    sourceFileDescriptors: FileDescriptorProto[];
-    /**
-     * The version number of protocol compiler.
-     *
-     * @generated from field: optional google.protobuf.compiler.Version compiler_version = 3;
-     */
-    compilerVersion?: Version | undefined;
-};
-/**
- * An encoded CodeGeneratorRequest is written to the plugin's stdin.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorRequest
- */
-export type CodeGeneratorRequestJson = {
-    /**
-     * The .proto files that were explicitly listed on the command-line.  The
-     * code generator should generate code only for these files.  Each file's
-     * descriptor will be included in proto_file, below.
-     *
-     * @generated from field: repeated string file_to_generate = 1;
-     */
-    fileToGenerate?: string[];
-    /**
-     * The generator parameter passed on the command-line.
-     *
-     * @generated from field: optional string parameter = 2;
-     */
-    parameter?: string;
-    /**
-     * FileDescriptorProtos for all files in files_to_generate and everything
-     * they import.  The files will appear in topological order, so each file
-     * appears before any file that imports it.
-     *
-     * Note: the files listed in files_to_generate will include runtime-retention
-     * options only, but all other files will include source-retention options.
-     * The source_file_descriptors field below is available in case you need
-     * source-retention options for files_to_generate.
-     *
-     * protoc guarantees that all proto_files will be written after
-     * the fields above, even though this is not technically guaranteed by the
-     * protobuf wire format.  This theoretically could allow a plugin to stream
-     * in the FileDescriptorProtos and handle them one by one rather than read
-     * the entire set into memory at once.  However, as of this writing, this
-     * is not similarly optimized on protoc's end -- it will store all fields in
-     * memory at once before sending them to the plugin.
-     *
-     * Type names of fields and extensions in the FileDescriptorProto are always
-     * fully qualified.
-     *
-     * @generated from field: repeated google.protobuf.FileDescriptorProto proto_file = 15;
-     */
-    protoFile?: FileDescriptorProtoJson[];
-    /**
-     * File descriptors with all options, including source-retention options.
-     * These descriptors are only provided for the files listed in
-     * files_to_generate.
-     *
-     * @generated from field: repeated google.protobuf.FileDescriptorProto source_file_descriptors = 17;
-     */
-    sourceFileDescriptors?: FileDescriptorProtoJson[];
-    /**
-     * The version number of protocol compiler.
-     *
-     * @generated from field: optional google.protobuf.compiler.Version compiler_version = 3;
-     */
-    compilerVersion?: VersionJson;
-};
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorRequest.
- * Use `create(CodeGeneratorRequestSchema)` to create a new message.
- */
-export declare const CodeGeneratorRequestSchema: GenMessage<CodeGeneratorRequest, {
-    jsonType: CodeGeneratorRequestJson;
-}>;
-/**
- * The plugin writes an encoded CodeGeneratorResponse to stdout.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorResponse
- */
-export type CodeGeneratorResponse = Message<"google.protobuf.compiler.CodeGeneratorResponse"> & {
-    /**
-     * Error message.  If non-empty, code generation failed.  The plugin process
-     * should exit with status code zero even if it reports an error in this way.
-     *
-     * This should be used to indicate errors in .proto files which prevent the
-     * code generator from generating correct code.  Errors which indicate a
-     * problem in protoc itself -- such as the input CodeGeneratorRequest being
-     * unparseable -- should be reported by writing a message to stderr and
-     * exiting with a non-zero status code.
-     *
-     * @generated from field: optional string error = 1;
-     */
-    error: string;
-    /**
-     * A bitmask of supported features that the code generator supports.
-     * This is a bitwise "or" of values from the Feature enum.
-     *
-     * @generated from field: optional uint64 supported_features = 2;
-     */
-    supportedFeatures: bigint;
-    /**
-     * The minimum edition this plugin supports.  This will be treated as an
-     * Edition enum, but we want to allow unknown values.  It should be specified
-     * according the edition enum value, *not* the edition number.  Only takes
-     * effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
-     *
-     * @generated from field: optional int32 minimum_edition = 3;
-     */
-    minimumEdition: number;
-    /**
-     * The maximum edition this plugin supports.  This will be treated as an
-     * Edition enum, but we want to allow unknown values.  It should be specified
-     * according the edition enum value, *not* the edition number.  Only takes
-     * effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
-     *
-     * @generated from field: optional int32 maximum_edition = 4;
-     */
-    maximumEdition: number;
-    /**
-     * @generated from field: repeated google.protobuf.compiler.CodeGeneratorResponse.File file = 15;
-     */
-    file: CodeGeneratorResponse_File[];
-};
-/**
- * The plugin writes an encoded CodeGeneratorResponse to stdout.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorResponse
- */
-export type CodeGeneratorResponseJson = {
-    /**
-     * Error message.  If non-empty, code generation failed.  The plugin process
-     * should exit with status code zero even if it reports an error in this way.
-     *
-     * This should be used to indicate errors in .proto files which prevent the
-     * code generator from generating correct code.  Errors which indicate a
-     * problem in protoc itself -- such as the input CodeGeneratorRequest being
-     * unparseable -- should be reported by writing a message to stderr and
-     * exiting with a non-zero status code.
-     *
-     * @generated from field: optional string error = 1;
-     */
-    error?: string;
-    /**
-     * A bitmask of supported features that the code generator supports.
-     * This is a bitwise "or" of values from the Feature enum.
-     *
-     * @generated from field: optional uint64 supported_features = 2;
-     */
-    supportedFeatures?: string;
-    /**
-     * The minimum edition this plugin supports.  This will be treated as an
-     * Edition enum, but we want to allow unknown values.  It should be specified
-     * according the edition enum value, *not* the edition number.  Only takes
-     * effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
-     *
-     * @generated from field: optional int32 minimum_edition = 3;
-     */
-    minimumEdition?: number;
-    /**
-     * The maximum edition this plugin supports.  This will be treated as an
-     * Edition enum, but we want to allow unknown values.  It should be specified
-     * according the edition enum value, *not* the edition number.  Only takes
-     * effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
-     *
-     * @generated from field: optional int32 maximum_edition = 4;
-     */
-    maximumEdition?: number;
-    /**
-     * @generated from field: repeated google.protobuf.compiler.CodeGeneratorResponse.File file = 15;
-     */
-    file?: CodeGeneratorResponse_FileJson[];
-};
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorResponse.
- * Use `create(CodeGeneratorResponseSchema)` to create a new message.
- */
-export declare const CodeGeneratorResponseSchema: GenMessage<CodeGeneratorResponse, {
-    jsonType: CodeGeneratorResponseJson;
-}>;
-/**
- * Represents a single generated file.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorResponse.File
- */
-export type CodeGeneratorResponse_File = Message<"google.protobuf.compiler.CodeGeneratorResponse.File"> & {
-    /**
-     * The file name, relative to the output directory.  The name must not
-     * contain "." or ".." components and must be relative, not be absolute (so,
-     * the file cannot lie outside the output directory).  "/" must be used as
-     * the path separator, not "\".
-     *
-     * If the name is omitted, the content will be appended to the previous
-     * file.  This allows the generator to break large files into small chunks,
-     * and allows the generated text to be streamed back to protoc so that large
-     * files need not reside completely in memory at one time.  Note that as of
-     * this writing protoc does not optimize for this -- it will read the entire
-     * CodeGeneratorResponse before writing files to disk.
-     *
-     * @generated from field: optional string name = 1;
-     */
-    name: string;
-    /**
-     * If non-empty, indicates that the named file should already exist, and the
-     * content here is to be inserted into that file at a defined insertion
-     * point.  This feature allows a code generator to extend the output
-     * produced by another code generator.  The original generator may provide
-     * insertion points by placing special annotations in the file that look
-     * like:
-     *   @@protoc_insertion_point(NAME)
-     * The annotation can have arbitrary text before and after it on the line,
-     * which allows it to be placed in a comment.  NAME should be replaced with
-     * an identifier naming the point -- this is what other generators will use
-     * as the insertion_point.  Code inserted at this point will be placed
-     * immediately above the line containing the insertion point (thus multiple
-     * insertions to the same point will come out in the order they were added).
-     * The double-@ is intended to make it unlikely that the generated code
-     * could contain things that look like insertion points by accident.
-     *
-     * For example, the C++ code generator places the following line in the
-     * .pb.h files that it generates:
-     *   // @@protoc_insertion_point(namespace_scope)
-     * This line appears within the scope of the file's package namespace, but
-     * outside of any particular class.  Another plugin can then specify the
-     * insertion_point "namespace_scope" to generate additional classes or
-     * other declarations that should be placed in this scope.
-     *
-     * Note that if the line containing the insertion point begins with
-     * whitespace, the same whitespace will be added to every line of the
-     * inserted text.  This is useful for languages like Python, where
-     * indentation matters.  In these languages, the insertion point comment
-     * should be indented the same amount as any inserted code will need to be
-     * in order to work correctly in that context.
-     *
-     * The code generator that generates the initial file and the one which
-     * inserts into it must both run as part of a single invocation of protoc.
-     * Code generators are executed in the order in which they appear on the
-     * command line.
-     *
-     * If |insertion_point| is present, |name| must also be present.
-     *
-     * @generated from field: optional string insertion_point = 2;
-     */
-    insertionPoint: string;
-    /**
-     * The file contents.
-     *
-     * @generated from field: optional string content = 15;
-     */
-    content: string;
-    /**
-     * Information describing the file content being inserted. If an insertion
-     * point is used, this information will be appropriately offset and inserted
-     * into the code generation metadata for the generated files.
-     *
-     * @generated from field: optional google.protobuf.GeneratedCodeInfo generated_code_info = 16;
-     */
-    generatedCodeInfo?: GeneratedCodeInfo | undefined;
-};
-/**
- * Represents a single generated file.
- *
- * @generated from message google.protobuf.compiler.CodeGeneratorResponse.File
- */
-export type CodeGeneratorResponse_FileJson = {
-    /**
-     * The file name, relative to the output directory.  The name must not
-     * contain "." or ".." components and must be relative, not be absolute (so,
-     * the file cannot lie outside the output directory).  "/" must be used as
-     * the path separator, not "\".
-     *
-     * If the name is omitted, the content will be appended to the previous
-     * file.  This allows the generator to break large files into small chunks,
-     * and allows the generated text to be streamed back to protoc so that large
-     * files need not reside completely in memory at one time.  Note that as of
-     * this writing protoc does not optimize for this -- it will read the entire
-     * CodeGeneratorResponse before writing files to disk.
-     *
-     * @generated from field: optional string name = 1;
-     */
-    name?: string;
-    /**
-     * If non-empty, indicates that the named file should already exist, and the
-     * content here is to be inserted into that file at a defined insertion
-     * point.  This feature allows a code generator to extend the output
-     * produced by another code generator.  The original generator may provide
-     * insertion points by placing special annotations in the file that look
-     * like:
-     *   @@protoc_insertion_point(NAME)
-     * The annotation can have arbitrary text before and after it on the line,
-     * which allows it to be placed in a comment.  NAME should be replaced with
-     * an identifier naming the point -- this is what other generators will use
-     * as the insertion_point.  Code inserted at this point will be placed
-     * immediately above the line containing the insertion point (thus multiple
-     * insertions to the same point will come out in the order they were added).
-     * The double-@ is intended to make it unlikely that the generated code
-     * could contain things that look like insertion points by accident.
-     *
-     * For example, the C++ code generator places the following line in the
-     * .pb.h files that it generates:
-     *   // @@protoc_insertion_point(namespace_scope)
-     * This line appears within the scope of the file's package namespace, but
-     * outside of any particular class.  Another plugin can then specify the
-     * insertion_point "namespace_scope" to generate additional classes or
-     * other declarations that should be placed in this scope.
-     *
-     * Note that if the line containing the insertion point begins with
-     * whitespace, the same whitespace will be added to every line of the
-     * inserted text.  This is useful for languages like Python, where
-     * indentation matters.  In these languages, the insertion point comment
-     * should be indented the same amount as any inserted code will need to be
-     * in order to work correctly in that context.
-     *
-     * The code generator that generates the initial file and the one which
-     * inserts into it must both run as part of a single invocation of protoc.
-     * Code generators are executed in the order in which they appear on the
-     * command line.
-     *
-     * If |insertion_point| is present, |name| must also be present.
-     *
-     * @generated from field: optional string insertion_point = 2;
-     */
-    insertionPoint?: string;
-    /**
-     * The file contents.
-     *
-     * @generated from field: optional string content = 15;
-     */
-    content?: string;
-    /**
-     * Information describing the file content being inserted. If an insertion
-     * point is used, this information will be appropriately offset and inserted
-     * into the code generation metadata for the generated files.
-     *
-     * @generated from field: optional google.protobuf.GeneratedCodeInfo generated_code_info = 16;
-     */
-    generatedCodeInfo?: GeneratedCodeInfoJson;
-};
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorResponse.File.
- * Use `create(CodeGeneratorResponse_FileSchema)` to create a new message.
- */
-export declare const CodeGeneratorResponse_FileSchema: GenMessage<CodeGeneratorResponse_File, {
-    jsonType: CodeGeneratorResponse_FileJson;
-}>;
-/**
- * Sync with code_generator.h.
- *
- * @generated from enum google.protobuf.compiler.CodeGeneratorResponse.Feature
- */
-export declare enum CodeGeneratorResponse_Feature {
-    /**
-     * @generated from enum value: FEATURE_NONE = 0;
-     */
-    NONE = 0,
-    /**
-     * @generated from enum value: FEATURE_PROTO3_OPTIONAL = 1;
-     */
-    PROTO3_OPTIONAL = 1,
-    /**
-     * @generated from enum value: FEATURE_SUPPORTS_EDITIONS = 2;
-     */
-    SUPPORTS_EDITIONS = 2
-}
-/**
- * Sync with code_generator.h.
- *
- * @generated from enum google.protobuf.compiler.CodeGeneratorResponse.Feature
- */
-export type CodeGeneratorResponse_FeatureJson = "FEATURE_NONE" | "FEATURE_PROTO3_OPTIONAL" | "FEATURE_SUPPORTS_EDITIONS";
-/**
- * Describes the enum google.protobuf.compiler.CodeGeneratorResponse.Feature.
- */
-export declare const CodeGeneratorResponse_FeatureSchema: GenEnum<CodeGeneratorResponse_Feature, CodeGeneratorResponse_FeatureJson>;

package/node_modules/@bufbuild/protobuf/dist/cjs/wkt/gen/google/protobuf/compiler/plugin_pb.js

@@ -1,68 +0,0 @@
-"use strict";
-// Copyright 2021-2026 Buf Technologies, Inc.
-//
-// Licensed under the Apache License, Version 2.0 (the "License");
-// you may not use this file except in compliance with the License.
-// You may obtain a copy of the License at
-//
-//      http://www.apache.org/licenses/LICENSE-2.0
-//
-// Unless required by applicable law or agreed to in writing, software
-// distributed under the License is distributed on an "AS IS" BASIS,
-// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-// See the License for the specific language governing permissions and
-// limitations under the License.
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.CodeGeneratorResponse_FeatureSchema = exports.CodeGeneratorResponse_Feature = exports.CodeGeneratorResponse_FileSchema = exports.CodeGeneratorResponseSchema = exports.CodeGeneratorRequestSchema = exports.VersionSchema = exports.file_google_protobuf_compiler_plugin = void 0;
-const file_js_1 = require("../../../../../codegenv2/file.js");
-const descriptor_pb_js_1 = require("../descriptor_pb.js");
-const message_js_1 = require("../../../../../codegenv2/message.js");
-const enum_js_1 = require("../../../../../codegenv2/enum.js");
-/**
- * Describes the file google/protobuf/compiler/plugin.proto.
- */
-exports.file_google_protobuf_compiler_plugin = (0, file_js_1.fileDesc)("CiVnb29nbGUvcHJvdG9idWYvY29tcGlsZXIvcGx1Z2luLnByb3RvEhhnb29nbGUucHJvdG9idWYuY29tcGlsZXIiRgoHVmVyc2lvbhINCgVtYWpvchgBIAEoBRINCgVtaW5vchgCIAEoBRINCgVwYXRjaBgDIAEoBRIOCgZzdWZmaXgYBCABKAkigQIKFENvZGVHZW5lcmF0b3JSZXF1ZXN0EhgKEGZpbGVfdG9fZ2VuZXJhdGUYASADKAkSEQoJcGFyYW1ldGVyGAIgASgJEjgKCnByb3RvX2ZpbGUYDyADKAsyJC5nb29nbGUucHJvdG9idWYuRmlsZURlc2NyaXB0b3JQcm90bxJFChdzb3VyY2VfZmlsZV9kZXNjcmlwdG9ycxgRIAMoCzIkLmdvb2dsZS5wcm90b2J1Zi5GaWxlRGVzY3JpcHRvclByb3RvEjsKEGNvbXBpbGVyX3ZlcnNpb24YAyABKAsyIS5nb29nbGUucHJvdG9idWYuY29tcGlsZXIuVmVyc2lvbiKSAwoVQ29kZUdlbmVyYXRvclJlc3BvbnNlEg0KBWVycm9yGAEgASgJEhoKEnN1cHBvcnRlZF9mZWF0dXJlcxgCIAEoBBIXCg9taW5pbXVtX2VkaXRpb24YAyABKAUSFwoPbWF4aW11bV9lZGl0aW9uGAQgASgFEkIKBGZpbGUYDyADKAsyNC5nb29nbGUucHJvdG9idWYuY29tcGlsZXIuQ29kZUdlbmVyYXRvclJlc3BvbnNlLkZpbGUafwoERmlsZRIMCgRuYW1lGAEgASgJEhcKD2luc2VydGlvbl9wb2ludBgCIAEoCRIPCgdjb250ZW50GA8gASgJEj8KE2dlbmVyYXRlZF9jb2RlX2luZm8YECABKAsyIi5nb29nbGUucHJvdG9idWYuR2VuZXJhdGVkQ29kZUluZm8iVwoHRmVhdHVyZRIQCgxGRUFUVVJFX05PTkUQABIbChdGRUFUVVJFX1BST1RPM19PUFRJT05BTBABEh0KGUZFQVRVUkVfU1VQUE9SVFNfRURJVElPTlMQAkJyChxjb20uZ29vZ2xlLnByb3RvYnVmLmNvbXBpbGVyQgxQbHVnaW5Qcm90b3NaKWdvb2dsZS5nb2xhbmcub3JnL3Byb3RvYnVmL3R5cGVzL3BsdWdpbnBiqgIYR29vZ2xlLlByb3RvYnVmLkNvbXBpbGVy", [descriptor_pb_js_1.file_google_protobuf_descriptor]);
-/**
- * Describes the message google.protobuf.compiler.Version.
- * Use `create(VersionSchema)` to create a new message.
- */
-exports.VersionSchema = (0, message_js_1.messageDesc)(exports.file_google_protobuf_compiler_plugin, 0);
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorRequest.
- * Use `create(CodeGeneratorRequestSchema)` to create a new message.
- */
-exports.CodeGeneratorRequestSchema = (0, message_js_1.messageDesc)(exports.file_google_protobuf_compiler_plugin, 1);
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorResponse.
- * Use `create(CodeGeneratorResponseSchema)` to create a new message.
- */
-exports.CodeGeneratorResponseSchema = (0, message_js_1.messageDesc)(exports.file_google_protobuf_compiler_plugin, 2);
-/**
- * Describes the message google.protobuf.compiler.CodeGeneratorResponse.File.
- * Use `create(CodeGeneratorResponse_FileSchema)` to create a new message.
- */
-exports.CodeGeneratorResponse_FileSchema = (0, message_js_1.messageDesc)(exports.file_google_protobuf_compiler_plugin, 2, 0);
-/**
- * Sync with code_generator.h.
- *
- * @generated from enum google.protobuf.compiler.CodeGeneratorResponse.Feature
- */
-var CodeGeneratorResponse_Feature;
-(function (CodeGeneratorResponse_Feature) {
-    /**
-     * @generated from enum value: FEATURE_NONE = 0;
-     */
-    CodeGeneratorResponse_Feature[CodeGeneratorResponse_Feature["NONE"] = 0] = "NONE";
-    /**
-     * @generated from enum value: FEATURE_PROTO3_OPTIONAL = 1;
-     */
-    CodeGeneratorResponse_Feature[CodeGeneratorResponse_Feature["PROTO3_OPTIONAL"] = 1] = "PROTO3_OPTIONAL";
-    /**
-     * @generated from enum value: FEATURE_SUPPORTS_EDITIONS = 2;
-     */
-    CodeGeneratorResponse_Feature[CodeGeneratorResponse_Feature["SUPPORTS_EDITIONS"] = 2] = "SUPPORTS_EDITIONS";
-})(CodeGeneratorResponse_Feature || (exports.CodeGeneratorResponse_Feature = CodeGeneratorResponse_Feature = {}));
-/**
- * Describes the enum google.protobuf.compiler.CodeGeneratorResponse.Feature.
- */
-exports.CodeGeneratorResponse_FeatureSchema = (0, enum_js_1.enumDesc)(exports.file_google_protobuf_compiler_plugin, 2, 0);

package/node_modules/@bufbuild/protobuf/dist/cjs/wkt/gen/google/protobuf/cpp_features_pb.d.ts

@@ -1,91 +0,0 @@
-import type { GenEnum, GenExtension, GenFile, GenMessage } from "../../../../codegenv2/types.js";
-import type { FeatureSet } from "./descriptor_pb.js";
-import type { Message } from "../../../../types.js";
-/**
- * Describes the file google/protobuf/cpp_features.proto.
- */
-export declare const file_google_protobuf_cpp_features: GenFile;
-/**
- * @generated from message pb.CppFeatures
- */
-export type CppFeatures = Message<"pb.CppFeatures"> & {
-    /**
-     * Whether or not to treat an enum field as closed.  This option is only
-     * applicable to enum fields, and will be removed in the future.  It is
-     * consistent with the legacy behavior of using proto3 enum types for proto2
-     * fields.
-     *
-     * @generated from field: optional bool legacy_closed_enum = 1;
-     */
-    legacyClosedEnum: boolean;
-    /**
-     * @generated from field: optional pb.CppFeatures.StringType string_type = 2;
-     */
-    stringType: CppFeatures_StringType;
-    /**
-     * @generated from field: optional bool enum_name_uses_string_view = 3;
-     */
-    enumNameUsesStringView: boolean;
-};
-/**
- * @generated from message pb.CppFeatures
- */
-export type CppFeaturesJson = {
-    /**
-     * Whether or not to treat an enum field as closed.  This option is only
-     * applicable to enum fields, and will be removed in the future.  It is
-     * consistent with the legacy behavior of using proto3 enum types for proto2
-     * fields.
-     *
-     * @generated from field: optional bool legacy_closed_enum = 1;
-     */
-    legacyClosedEnum?: boolean;
-    /**
-     * @generated from field: optional pb.CppFeatures.StringType string_type = 2;
-     */
-    stringType?: CppFeatures_StringTypeJson;
-    /**
-     * @generated from field: optional bool enum_name_uses_string_view = 3;
-     */
-    enumNameUsesStringView?: boolean;
-};
-/**
- * Describes the message pb.CppFeatures.
- * Use `create(CppFeaturesSchema)` to create a new message.
- */
-export declare const CppFeaturesSchema: GenMessage<CppFeatures, {
-    jsonType: CppFeaturesJson;
-}>;
-/**
- * @generated from enum pb.CppFeatures.StringType
- */
-export declare enum CppFeatures_StringType {
-    /**
-     * @generated from enum value: STRING_TYPE_UNKNOWN = 0;
-     */
-    STRING_TYPE_UNKNOWN = 0,
-    /**
-     * @generated from enum value: VIEW = 1;
-     */
-    VIEW = 1,
-    /**
-     * @generated from enum value: CORD = 2;
-     */
-    CORD = 2,
-    /**
-     * @generated from enum value: STRING = 3;
-     */
-    STRING = 3
-}
-/**
- * @generated from enum pb.CppFeatures.StringType
- */
-export type CppFeatures_StringTypeJson = "STRING_TYPE_UNKNOWN" | "VIEW" | "CORD" | "STRING";
-/**
- * Describes the enum pb.CppFeatures.StringType.
- */
-export declare const CppFeatures_StringTypeSchema: GenEnum<CppFeatures_StringType, CppFeatures_StringTypeJson>;
-/**
- * @generated from extension: optional pb.CppFeatures cpp = 1000;
- */
-export declare const cpp: GenExtension<FeatureSet, CppFeatures>;