OpenTelemetry types package renaming

[dyladan]

Hello. I am one of the maintainers of the OpenTelemetry JS project. This is not a bug or a feature request.

The OpenTelemetry JS project is renaming the @opentelemetry/types package to @opentelemetry/api and bringing all API related concerns which used to reside in @opentelemetry/core into the new package. This change is intended to make it so that library vendors can rely on only the @opentelemetry/api package. The change can be viewed here (open-telemetry/opentelemetry-js#727) and motivation for the change can be viewed here (open-telemetry/opentelemetry-js#721).

I see that you currently depend on the types package, which will be deprecated shortly. https://github.com/Azure/azure-sdk-for-js/search?l=JSON&q=%22opentelemetry%2Ftypes%22

Please reach out to myself or @mayurkale22 if you have any questions.

[jongio]

I get the following when installing @azure/keyvault-secrets

npm WARN deprecated @opentelemetry/[email protected]: Package renamed to @opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js

[mayurkale22]

We rename the package from @opentelemetry/types to @opentelemetry/api since 0.4.0.

[jongio]

Are you saying this is resolved and waiting to be deployed? If so, could you ref the PR here?

[mayurkale22]

@opentelemetry/api is already published to npm. This is the PR: open-telemetry/opentelemetry-js#727

[jongio]

Correct, My comment was to confirm that we are still referencing types. Need to update to api.

[dyladan]

This repo is still referencing types and needs to be updated to reference api. I also suggest that you change your semver scheme from ^x.y.z to either ~x.y.z or lock versions with x.y.z otherwise you may receive breaking changes during updates until we reach stable 1.0.0.

[xirzec]

@jongio are you blocked by this? Our plan was to release our final preview with OT beta (eta Mar 16)

@dyladan caret ranges for 0.x.x work differently than after major version 1. Specifically, caret does not allow the left-most non-zero value to change. E.g. ^0.3.0 will not accept 0.4.0 or higher. source: https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004

[jongio]

No. Just included in case someone Googles that message.

[tibor19]

@xirzec @mayurkale22 I am blocked by this change. I am trying to use Azure storage-blob to create a github action, and it fails with this error:
Error: Cannot find module '/home/runner/work/_actions/tibor19/Azure-Storage-Action/node-only/node_modules/@opentelemetry/types/build/src/index.js'. Please verify that the package.json has a valid "main" entry

[xirzec]

Error: Cannot find module '/home/runner/work/_actions/tibor19/Azure-Storage-Action/node-only/node_modules/@opentelemetry/types/build/src/index.js'. Please verify that the package.json has a valid "main" entry

This looks like a bundler is expecting an ES module rather than a CJS export? I'm not sure if the new OT package will help if it's not exporting modules.

[xirzec]

This work is now live on NPM: https://www.npmjs.com/package/@azure/core-tracing/v/1.0.0-preview.8