Closed
Description
Problem
Specifying "unstable": ["otel"]
in deno.json does not enable otel signals while specifying --unstable-otel
in the run command does.
A similar issue was raised in #27273 but otel enabling was since refactored in #27333 so I believe this is a different problem.
Expected behavior
both "unstable": ["otel"]
and --unstable otel
should work to trigger the otel unstable feature flag
Actual behavior
"unstable": ["otel"]
does not seem to do anything while --unstable otel
works.
Environment
Deno v2.3.3
Metadata
Metadata
Assignees
Labels
No labels