[Feature request] Implement module entry point ES6 exports to support tree-shaking

[Havunen]

Hey!

It would be nice to be able to import only the things we need from this library. For example when we are not using pulse or other tracking features. Those could be stripped out from the bundle.

https://webpack.js.org/guides/tree-shaking/
https://medium.com/@netxm/what-is-tree-shaking-de7c6be5cadd
https://medium.com/@Rich_Harris/tree-shaking-versus-dead-code-elimination-d3765df85c80

[BenjaminHarding]

This would definitely be useful to have. I think in order to support this we would have to restructure how the library is used currently and so wouldn't be a quick thing we can roll out but I'll add it to the radar for us to consider in the future :)

[pbessone]

Since version 10, Angular has started to warn about projects not using ES modules and don't support tree shaking.
These warnings can be ignored but it would be good if we could see some traction implementing this feature.

[mduncan26]

Hi @pbessone

Thank you for letting us know. I have passed on this feedback onto the product team here at Raygun. They will consider this when updating the roadmap for the products. Unfortunately this will not be available in the short term, but we will update this thread once we have more information.

Thank you,
Mitchell.

[akauppi]

@mduncan26 Nice to see recent activity on this! I filed a customer request (23657) last week. Could you check that out and align with the product team?

It’s about allowing easy use of Raygun for users of this open source web app template: https://github.com/akauppi/GroundLevel-firebase-es

[burymm]

Any updates on this?

[sumitramanga]

Hi there,

This is still on our feature request list but we haven't forgotten about it! We can continue to keep this thread open in the mean time and let you all know when this feature request gets picked up.

Thank you for your patience!