Next.js + Turbopack: `thirdPartyErrorFilterIntegration` (`applicationKey`)

[FabianKoder]

Problem Statement

It is currently not possible to use the thirdPartyErrorFilterIntegration integration when utilizing Turbopack.

Solution Brainstorm

I am not sure how exactly the application key works, but my first guess would be that it is kind of similar to debug IDs. Since that feature is already working with Turbopack, there may be a similar approach to inject application keys?

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1710

[chargome]

Hey @FabianKoder – thanks for reaching out. We'll investigate for a workaround for the bundler plugin approach, but with the current turbopack architecture this might not be feasible.

[erakor]

Seconded. Since migrating to Turbopack and, therefore getting rid of thirdPartyErrorFilterIntegration, issue count triggered by tags (we have Google Tag Manager enabled) has skyrocketed. We've been trying to fine beforeSend without much success. The noise is getting serious.

If a similar solution to thirdPartyErrorFilterIntegration is not possible for Turbopack, I'd love to hear how anyone else managed to filter third-party errors from getting reported. Much appreciated.