Skip to content

Commit e2ac867

Browse files
lizokmLms24
andauthored
Update docs/platforms/javascript/common/best-practices/micro-frontends.mdx
Co-authored-by: Lukas Stracke <[email protected]>
1 parent 1a1c411 commit e2ac867

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/platforms/javascript/common/best-practices/micro-frontends.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ keywords:
2525
In order for the Sentry JavaScript SDK to work with your micro frontends, make sure that all micro frontends that import from an `@sentry/*` package are using the same version of the Sentry SDK.
2626
</Alert>
2727

28-
If your app uses micro frontends, it’s very useful to be able to track which one an error is coming from. To do this with Sentry, you can create either an automatic or a manual setup where you send events to separate Sentry projects representing each of your micro frontend services. This makes it easier to see what’s going wrong and where, helping you track issues and fix them faster, especially in complex frontend architectures.
28+
If your app uses micro frontends, it’s very useful to be able to track which one an error is coming from. To do this with Sentry, you can create either an automatic or a manual setup where you send events to separate Sentry projects representing each of your micro frontends. This makes it easier to see what’s going wrong and where, helping you track issues and fix them faster, especially in complex frontend architectures.
2929

3030
Below you'll find setup instructions for both an automatic and a manual way to route errors to different Sentry projects.
3131

0 commit comments

Comments
 (0)