feat: upload source maps to Datadog during MFE deploy #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related PR: https://github.com/edx/edx-internal/pull/10993
https://docs.datadoghq.com/real_user_monitoring/guide/upload-javascript-source-maps/
Without source maps uploaded to Datadog for MFEs, any reported JS errors are largely not actionable as engineers cannot discern which specific area of code caused the exception due to minified production JS code.
Example from Datadog docs:
Without source maps
JS error without any clues to to which code area/path triggered the error:
With source maps
Human-readable unminified source code of the exact line of JS code that triggered the error, including a direct link to source code on GitHub: