docs(js): Add CDN tab to manual multiplexed transport examples#17334
Merged
docs(js): Add CDN tab to manual multiplexed transport examples#17334
Conversation
Add CDN/Loader Bundle code tabs alongside the existing NPM examples in the 'Manually Route Errors to Different Projects' section of the micro-frontends best practices page. Both the 'Using the Default Matcher' and 'Using a Custom Matcher' sections now show how to load bundle.min.js + multiplexedtransport.min.js from the CDN and then call Sentry.makeMultiplexedTransport / Sentry.captureException using the global Sentry object, consistent with the CDN tab pattern already present in the 'Automatically Route Errors' section above.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Lms24
approved these changes
Apr 14, 2026
Member
Lms24
left a comment
Lms24
left a comment
There was a problem hiding this comment.
well... that went better than expected 😅
Lms24
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds CDN/Loader Bundle code tabs to the Manually Route Errors to Different Projects section of the micro-frontends best practices page.
Previously, the 'Automatically Route Errors' section already had NPM + CDN tabs, but both manual sub-sections ('Using the Default Matcher' and 'Using a Custom Matcher') only showed NPM code.
Changes
bundle.min.js+multiplexedtransport.min.jsand callsSentry.makeMultiplexedTransport/Sentry.captureExceptionvia the globalSentryobject, includingSentry.MULTIPLEXED_TRANSPORT_EXTRA_KEY.jsfences tojavascript {tabTitle:NPM}to match the tab convention used in the rest of the file.The pattern follows the existing CDN tab in the 'Automatically Route Errors' section directly above, using the same
@injectversion/checksum helpers for integrity attributes.Fixes a gap reported via Slack support where CDN-only users (e.g. customers not bundling) couldn't find guidance on using
makeMultiplexedTransportwithout npm.