Nev

I believe that this issue should now be closed based on the outcome and [this PR](https://github.com/open-telemetry/opentelemetry-specification/pull/3858) which prohibits "standard" attributes from evolving to contain complex types. We should have all...

> @MSNev @martinkuba how important is it for this event to exactly match the browser event? or would it be ok as long as you have the ability to capture...

> @MSNev @martinkuba how important is it for this event to exactly match the browser event? Very important, as anyone upgrading from something other than OTel would end up with...

This seems like a issue with the way your build system is creating your map files? > @nevware21\ts-async\bundle\es5\ts-polyfills-async.js The Application Insights SDK doesn't actually use this file and you don't...

Another comment on the reference (which may just be an example that you have provided, but calling out for anyone else who may see this). Unless you know you are...

Ah..., I understand now... Because we are creating "single" export definitions (which are referenced in the package.json as the input) and they are using rollup to "package" the content, this...

Hmm, for the specific node_modules reference this looks like it might be a bug in rollup as according to [this documentation](https://rollupjs.org/configuration-options/#output-sourcemapignorelist) if we don't specify anything then all files with...

Yeah, I'm working on fixing the AI stuff for our final release of the year next week. But one thing I've noticed with the changes to ts-utils is that our...

Based on what the Copilot PR generated, I think this is now fixed (from the perspective of the generated map files in the current releases) based on the @nevware21 packages...

Ok, sorry for the delay in responding as I've been unexpectedly away. So it seems like we should apply the same type of rewriting of the map files :-( to...