Report an app's errors to your own Sentry project
Settings › Integrations has Sentry: paste your project's DSN and anything an app's actions throw is reported there, in development and production, tagged with the action, its phase, the store and the run's event in Logs. Errors your code catches go with captureException from the SDK.
The DSN is saved as SENTRY_DSN for both environments. Development reports once its dev server restarts and production from its next deploy, each under its own environment name, with production's file version as the release.
It sends Sentry's events over fetch, so there's no Sentry package to add and it works wherever the app runs. Tests run with ib-apps test never report, and pages under web/ aren't covered.
More in Errors in Sentry.