feat(nextjs): Add top-level applicationKey option#20794
Conversation
size-limit report 📦
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 79d9231. Configure here.
| }); | ||
|
|
||
| expect(result.applicationKey).toBe('my-app-key'); | ||
| }); |
There was a problem hiding this comment.
Feat PR missing integration or E2E test
Low Severity
This is a feat PR that adds a new top-level applicationKey option, but it only includes unit tests. Per the project review rules, feat PRs are expected to include at least one integration or E2E test. Consider adding an E2E test that verifies the applicationKey option works end-to-end for either webpack or turbopack builds, similar to the existing browser-webworker-vite E2E test that exercises applicationKey.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 79d9231. Configure here.
Adds a top-level
applicationKeyoption to SentryBuildOptions so users can configurethirdPartyErrorFilterIntegrationwithout needing experimental or unstable apis. Forwards to both webpack and turbopack.ref #17384