Benoît

> Sentry has a cool feature that records the session in case of an error automatically. We are aware of this and we are exploring ways of doing something similar....

We just realized an audit of our SDK bundled size. Here are the main efforts that we will work in the coming weeks/months: * [x] #1335 Drop old browsers support...

@fdc-viktor-luft We did consider creating a package supporting only ES6 syntax. It didn't yield significant-enough results to justify maintaining such package right now. Because [IE11 will be retired in june](https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/),...

While this is still a topic we have in mind, we don't have further work planed just yet appart from removing IE support, which would allow us to use shorter...

Thank you for your thorough report! We are looking into it. We'll keep you updated.

We are still figuring how to best handle this case. In the meantime I opened a Chromium issue: https://issues.chromium.org/issues/323703325

👋 I agree the documentation is a bit misleading. There might be an impact depending on how you are bundling the SDK code inside your application. If it's in a...

We are still working on improving the sub-app use cases. > One issue I have is that DD_RUM context gets reloaded and loses its internal context in child app I'm...

Thanks for the project example! Really useful. So it seems that the Browser SDK is included twice in the resulting bundles * http://localhost:3001/main.js * http://localhost:3002/vendors-node_modules_datadog_browser-rum_esm_entries_main_js.js Is this intended? It seems...

No update yet. Loading the SDK code multiple times on the same page would not be practical. If you have a specific use case in mind that is not yet...