You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of the source-map devtool in the default production config (imported here) has been identified as a way to generate stack traces for New Relic's APM solution. This increases the build size by up to 10MB, but since it is not served to the browser, it is not necessarily a concern for organizations that are not using New Relic.
However, this raises the question of finding an open source alternative that serves the same purpose, via the same source-map devtool, testing it, and then recommending it to the community at large.
@jmbowman has put together a great list of potential alternatives:
The use of the
source-map
devtool in the default production config (imported here) has been identified as a way to generate stack traces for New Relic's APM solution. This increases the build size by up to 10MB, but since it is not served to the browser, it is not necessarily a concern for organizations that are not using New Relic.However, this raises the question of finding an open source alternative that serves the same purpose, via the same
source-map
devtool, testing it, and then recommending it to the community at large.@jmbowman has put together a great list of potential alternatives:
https://openedx.atlassian.net/wiki/spaces/AC/pages/3555754025/Application+Performance+Monitoring
The text was updated successfully, but these errors were encountered: