Include protos files in bundle directly

[polRk]

What happened?

I'm using esbuild to build my server in single .mjs file.
And i got an error with ReferenceError: __dirname is not defined

@opentelemetry/otlp-grpc-exporter-base/build/src/util.js
Try to load protos files in run time, not build time. Do not do that.

const includeDirs = [path.resolve(__dirname, "..", "protos")];
protoLoader2.load

Steps to Reproduce

Build project with esbuild

esbuild --platform=node --format=esm --bundle

Expected Result

Protos files present in library bundle in build time.

Actual Result

Library try to load protos in run time.

Additional Details

Building for esm, running in node 18.8

OpenTelemetry Setup Code

It doesn't metter

package.json

"@opentelemetry/api": "1.4.0",
    "@opentelemetry/exporter-metrics-otlp-grpc": "^0.35.1",
    "@opentelemetry/exporter-metrics-otlp-http": "0.35.1",
    "@opentelemetry/exporter-prometheus": "0.35.1",
    "@opentelemetry/exporter-trace-otlp-grpc": "0.35.1",
    "@opentelemetry/exporter-trace-otlp-http": "0.35.1",
    "@opentelemetry/instrumentation": "0.35.1",
    "@opentelemetry/instrumentation-graphql": "0.33.0",
    "@opentelemetry/instrumentation-grpc": "0.35.1",
    "@opentelemetry/instrumentation-http": "0.35.1",
    "@opentelemetry/resources": "1.9.1",
    "@opentelemetry/sdk-metrics": "1.9.1",
    "@opentelemetry/sdk-trace-node": "1.9.1",
    "@opentelemetry/semantic-conventions": "1.9.1",

Relevant log output

graphql  | file:///usr/home/app/server.mjs:26961
graphql  |       const includeDirs = [path.resolve(__dirname, "..", "protos")];
graphql  |                                         ^
graphql  | 
graphql  | ReferenceError: __dirname is not defined
graphql  |     at onInit (file:///usr/home/app/server.mjs:26961:41)
graphql  |     at Immediate.<anonymous> (file:///usr/home/app/server.mjs:27164:11)
graphql  |     at process.processImmediate (node:internal/timers:471:21)
graphql  | 
graphql  | Node.js v18.8.0

[dyladan]

I'm removing the bug label since we don't claim to support this. As you said, this is caused by dynamically loading proto files. There have been other requests for this in the past and they seem to be coming more frequently so we should probably look into this soon. I know some people have already done some work looking into statically generated grpc clients, but they ran into compatibility issues with our existing export transformations.