chore: update biome to v1.8.0

[anonrig]

I think the time has come to update Biome. My previous attempt to update was almost 3 months, which didn't get a single pull-request review: #10994

I recommend watching this: https://www.youtube.com/watch?v=Yv9tQRPf3nE

cc @getsentry/team-web-sdk-frontend

[mydea]

Let's talk about this some more, I think we are unlikely to merge this because we are still having too many problems with biome, sadly 😬 mainly they are problems with editor integrations (in VSCode, but even more so in IntelliJ), not biome itself, but it does not change the fact that it is sadly reducing our productivity, not increasing it. We'll probably look to revert back to use prettier overall, honestly - don't get me wrong, biome is cool and really fast, but the ability to ship stuff fast has the highest prio for us, and as of today it is not helping us in this regard (yet).

[anonrig]

New versions will likely fix your problems not add new pain points.

[AbhiPrasad]

I think the primary blocker is not from biome itself in this case, it's with the editor integrations. Considering that is disrupting people's workflows, I'm also in favour of holding off on biome and waiting for these integrations to improve.

[anonrig]

I think the primary blocker is not from biome itself in this case, it's with the editor integrations. Considering that is disrupting people's workflows, I'm also in favour of holding off on biome and waiting for these integrations to improve.

Editor integrations run the local biome binary. Updating local version will improve editor integrations since those integrations doesn't ship/bundle with their own Biome executable

[codecov]

❌ 13 Tests Failed:

Tests completed	Failed	Passed	Skipped
604	13	591	293

View the top 3 failed tests by shortest run time

performance.test.ts sends a lifecycle span for each tracked components

Stack Traces | 3.12s run time

performance.test.ts:126:1 sends a lifecycle span for each tracked components

performance.test.ts performance events › capture a distributed pageload trace

Stack Traces | 10.1s run time

performance.test.ts:6:3 capture a distributed pageload trace

performance.test.ts sends a pageload transaction with component tracking init spans

Stack Traces | 15.2s run time

performance.test.ts:4:1 sends a pageload transaction with component tracking init spans

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!

[Lms24]

hmm looks like biome doesn't play well with astro? These imports are not unused

[andreiborza]

:(

[anonrig]

unused rule can be disabled in override for urls ending with .astro

[Lms24]

Closing, we reverted to prettier for now