refactor: lazy-load sentry

[ovflowd]

Description

Sentry has an obnoxious big bundle-size which is non-tree-shakeable (mostly) due to its tracing/replay features.

After pondering a bit I've concluded the following:

• We don't need Sentry Tracing (Web Vitals / Client-Side Performance Analysis) as we already have Vercel Web Vitals and Performance Analysis (through vercel/analytics)
• We can lazy-load Sentry, as client-side errors should mostly not happen during-load. By lazy-loading (dynamic imports) we're just reducing the priority that Sentry has during load, and will delegate the Application to bootstrap first rather than Sentry
• I also disabled Sentry Replays as they use a big bundle size and for our use cases I doubt we really would benefit from Replays
• This change reduces the initial bundle size (pre-gzip) (and just an estimate) from 240Kb unto 150Kb and the first JS Load from 140 Kb to 90 Kb

Validation

We should still see Sentry reporting Errors on client-side and it should still do /monitoring API calls

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 17, 2023 11:26pm

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 100	🟢 97	🟠 83	🟢 92	🔗
/en/about	🟢 100	🟢 95	🟠 83	🟢 92	🔗
/en/about/previous-releases	🟢 100	🟢 96	🟠 83	🟢 92	🔗
/en/download	🟢 100	🟢 97	🟠 83	🟢 92	🔗
/en/blog	🟢 97	🟢 97	🟠 83	🟢 92	🔗

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	82.91% (398/480)	70.16% (87/124)	69.14% (65/94)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
71	0 💤	0 ❌	0 🔥	5.621s ⏱️

[bmuenzenmeyer]

• We don't need Sentry Tracing (Web Vitals / Client-Side Performance Analysis) as we already have Vercel Web Vitals and Performance Analysis (through vercel/analytics)

this thought crossed my mind too 👍

[bmuenzenmeyer]

all for iterating on what's best

[ovflowd]

cc @nodejs/web-infra I'm fast-tracking this for now. We might want to revisit the behaviour of Sentry Tracing as we have a meeting with Sentry next week.