ref(build): Use rollup config function for @sentry/browser
#4668
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.
As part of centralizing and unifying our CDN rollup config, this uses the config generation function introduced in #4650 to generate the config for all browser bundles.
Unlike many of the other PRs in this series, this one does actually have an effect on certain bundles, to wit:
_mergeOptions
is no longer a protected-from-minifcation property, as it's about to be extracted into a stand-alone function.Up until this point, one difference between the
@sentry/browser
rollup config and all of the other rollup configs was the former's use of the__SENTRY_NO_DEBUG__
flag to suppress logs in the minified bundles. Rather than add a parameter to the function controlling whether or not each package should use the flag, I decided it was better to just apply the flag to all minified bundles.Ref: https://getsentry.atlassian.net/browse/WEB-639