-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Sentry Error Filtering #772
Conversation
🦋 Changeset detectedLatest commit: 1004c70 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2150908543/npm-package-wrangler-772 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/772/npm-package-wrangler-772 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/2150908543/npm-package-wrangler-772 dev path/to/script.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should have a changeset, I think
43c9333
to
e8d1a8c
Compare
e8d1a8c
to
c13bbe6
Compare
…lare` in the frame
c13bbe6
to
1004c70
Compare
fix: We want to prevent any user created code from sending Events to Sentry,
which can be captured by
uncaughtExceptionMonitor
listener.Miniflare code can run user code on the same process as Wrangler, so we want to return
null
if "@miniflare" is present in the Event frames.