Commit 2140b53
authored
fix(nuxt): Ignore 300-400 status codes on app errors in Nuxt (#15473)
Before submitting a pull request, please take a look at our
[Contributing](https://github.com/getsentry/sentry-javascript/blob/master/CONTRIBUTING.md)
guidelines and verify:
- [ ] If you've added code that should be tested, please add tests.
- [ ] Ensure your code lints and the test suite passes (`yarn lint`) &
(`yarn test`).
### Description
I noticed that Nuxt 300-400 status codes from the app are being reported
to Sentry unnecessarily. There appears to be a guard against doing this
on the server side errors but client side errors like 404 or 401s are
being reported to Sentry.
I have simply added the same guard on the client side error reporter for
the Nuxt integration of Sentry.1 parent 0867a99 commit 2140b53
1 file changed
+7
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
66 | 66 | | |
67 | 67 | | |
68 | 68 | | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
69 | 75 | | |
70 | 76 | | |
71 | 77 | | |
| |||
0 commit comments