Test Next.js microfrontend setup

[chargome]

https://vercel.com/docs/microfrontends/quickstart is available in beta.

We need to investigate how compatible a MFE setup is with Sentry and possibly add an e2e test for this.

[logaretm]

I setup a microfrontend group on Vercel and in multi-zone apps we don't need to do anything as they are separate apps.

This means users will need to install Sentry SDK for each microfrontend (e.g: @sentry/nextjs and @sentry/sveltekit)

I did a small test with a Next.js + SvelteKit app combo and it works well:

So it feels like it would be a small note to add in Next.js documentation, It would be up to the user to set up a separate project with separate DSN for each or if both should use the same DSN. I think we should recommend the former since usually microfrontends are utilized by different teams.

I will work on adding the guide to the docs this week. In the future we could add a detector thing to the Sentry Wizard to auto install the projects but that's a can of worms since Vercel does not require the projects to be co-located within the same repository.

I will also investigate module federation setup to see if we need to do anything there as well.

[logaretm]

Nothing special to do when it is nextjs to nextjs apps either, but for SPA or module-federated micro frontends users should use our existing guide that covers that.

I don't think there is anything for us to do here other than perhaps improving the CLI/Wizard to specifically automate the instrumentation of the microfrontend apps. However since it is not required for these apps to be in the same repository it doesn't seem feasible without depending on Vercel's CLI.