Getting error "could not resolve" while doing npm i opentelemetry-instrumentation-elasticsearch #252
Description
Getting error "could not resolve" while doing npm i opentelemetry-instrumentation-elasticsearch
npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: undefined@undefined npm ERR! Found: @opentelemetry/api@1.1.0 npm ERR! node_modules/@opentelemetry/api npm ERR! @opentelemetry/api@"^1.0.0" from @opentelemetry/api-metrics@0.28.0 npm ERR! node_modules/@opentelemetry/api-metrics npm ERR! @opentelemetry/api-metrics@"0.28.0" from @opentelemetry/instrumentation@0.28.0 npm ERR! node_modules/@opentelemetry/instrumentation npm ERR! @opentelemetry/instrumentation@"0.28.0" from @opentelemetry/sdk-node@0.28.0 npm ERR! node_modules/@opentelemetry/sdk-node npm ERR! @opentelemetry/sdk-node@"^0.28.0" from the root project npm ERR! @opentelemetry/api-metrics@"0.28.0" from @opentelemetry/sdk-metrics-base@0.28.0 npm ERR! node_modules/@opentelemetry/sdk-metrics-base npm ERR! @opentelemetry/sdk-metrics-base@"0.28.0" from @opentelemetry/sdk-node@0.28.0 npm ERR! node_modules/@opentelemetry/sdk-node npm ERR! @opentelemetry/sdk-node@"^0.28.0" from the root project npm ERR! 1 more (@opentelemetry/sdk-node) npm ERR! peer @opentelemetry/api@"^1.0.2" from @opentelemetry/auto-instrumentations-node@0.28.0 npm ERR! node_modules/@opentelemetry/auto-instrumentations-node npm ERR! @opentelemetry/auto-instrumentations-node@"^0.28.0" from the root project npm ERR! 72 more (@opentelemetry/instrumentation, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! opentelemetry-instrumentation-elasticsearch@"*" from the root project npm ERR! npm ERR! Conflicting peer dependency: @opentelemetry/api@1.3.0 npm ERR! node_modules/@opentelemetry/api npm ERR! peer @opentelemetry/api@"^1.3.0" from opentelemetry-instrumentation-elasticsearch@0.34.0 npm ERR! node_modules/opentelemetry-instrumentation-elasticsearch npm ERR! opentelemetry-instrumentation-elasticsearch@"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.