@azure/storage-blob runtime TypeError: Cannot read property 'INTERNAL' of undefined

[voidfoo]

import { BlobServiceClient } from "https://cdn.skypack.dev/@azure/storage-blob/";

console.log('hello');

const client = new BlobServiceClient("endpoint");

client.getProperties().then((resp) => {
  console.log(resp);
})

stack trace:

core-tracing.js:368 Uncaught (in promise) TypeError: Cannot read property 'INTERNAL' of undefined
    at core-tracing.js:368
    at BlobServiceClient2.<anonymous> (storage-blob.js:20162)
    at step (tslib.js:221)
    at Object.next (tslib.js:168)
    at tslib.js:154
    at new Promise (<anonymous>)
    at __awaiter2 (tslib.js:136)
    at BlobServiceClient2.getProperties (storage-blob.js:20157)
    at pen.js?key=pen.js-09c6ac50-f140-7d00-144a-744a4d13913f:7

The code is trying to access SpanKind.INTERNAL which is from @ opentelemetry/api

import __commonjs_module0 from "/-/@opentelemetry/[email protected]/dist=es2020,mode=imports/optimized/@opentelemetry/api.js";
const {TraceFlags} = __commonjs_module0;
const {CanonicalCode} = __commonjs_module0;
const {SpanKind} = __commonjs_module0;

[vasco-santos]

Hello @voidfoo @natemoo-re @drwpow

I ran into the exact same problem when using skypack with a cjs module that depends on a module with multiple builds (cjs, esm, ..)

I nailed this down to a reproducible case that hopefully can get this easily fixed: https://github.com/vasco-santos/cjs-esm-skypack-build-rep

[voidfoo]

The latest @azure/storage-blob is now working fine with skypack