fix: Handle exceptions thrown from postcss when calling adaptCssForReplay

[guntherjh]

This PR adds a try/catch around postcss().process() so that exceptions won't cause playback to crash. I was encountering issues where invalid CSS was being passed to postcss which would result in CssSyntaxError. I am still investigating why invalid CSS is passed to adaptCssForReplay in the first place, but for now this change should at least make sure any exceptions from postcss are at least handled and logged. I am currently using warn to log the exceptions but am happy to switch that to something else if need be.

Related discussion in rrweb slack: https://rrweb.slack.com/archives/C01BYDC5C93/p1727975312250899

[changeset-bot]

🦋 Changeset detected

Latest commit: 27f01fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 19 packages

Name	Type
rrweb-snapshot	Patch
rrweb	Patch
rrdom	Patch
rrdom-nodejs	Patch
rrweb-player	Patch
@rrweb/all	Patch
@rrweb/replay	Patch
@rrweb/record	Patch
@rrweb/types	Patch
@rrweb/packer	Patch
@rrweb/utils	Patch
@rrweb/web-extension	Patch
rrvideo	Patch
@rrweb/rrweb-plugin-console-record	Patch
@rrweb/rrweb-plugin-console-replay	Patch
@rrweb/rrweb-plugin-sequential-id-record	Patch
@rrweb/rrweb-plugin-sequential-id-replay	Patch
@rrweb/rrweb-plugin-canvas-webrtc-record	Patch
@rrweb/rrweb-plugin-canvas-webrtc-replay	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[otan]

heads up, i think the root cause is #1575

[guntherjh]

@otan Good call out! That definitely seems like one of the ways invalid CSS can be passed to postcss. I'm also looking at another potential cause and will report back here if I find anything useful (or if it turns out to be the same problem as the one described in the issue you linked).

For this particular PR, I just wanted to simply make sure exceptions from postcss were handled so it wouldn't cause playback to crash.

[eoghanmurray]

#1600 should fix that those types of fragments get passed into postcss in the first place. Happy to add this try/except but hopefully it shouldn't be encountered after #1600 (assuming the underlying css is fine)

[guntherjh]

@eoghanmurray thanks for taking a look at my PR! I'll need to double check the original issue I was encountering to see if #1600 fixes it (I thought I checked and it didn't but I honestly can't remember 😓). In any case, I am inclined to keep the try/catch just to prevent any future exceptions from postcss from going unhandled. I'm happy to make any updates to how the exceptions are logged (or any other issue you see). Thanks again for the review!