chore: drop generate-protos.js in favor of npm script #6134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
See #6055
The script can be made to work on all platforms, but it's not necessary anymore since we only have one package that needs protos to be generated. Previously, we generated these for both the proto exporter base (which does not exist anymore) and the grpc exporter base which is why a script was easier to deal with. That functionality has been consolidated and moved to
@opentelemetry/otlp-transformerin #4542, removing the need to generate code in the exporter package itself in the cleanup steps that followed that PR.Supersedes #6055