octalmage/gatsby-plugin-sentry issues and pull requests

#27 - CORS fails when plugin is activated

Issue - State: open - Opened by jdozierezell about 4 years ago

#26 - Activation results in CORS errors

Issue - State: closed - Opened by jdozierezell about 4 years ago - 1 comment

#25 - Collect errors in the build stage

Issue - State: open - Opened by arthurzenika over 4 years ago - 5 comments

#24 - Working with beforeSend callback

Issue - State: open - Opened by BrOrlandi over 4 years ago - 3 comments

#23 - ReferenceError: Sentry is not defined

Issue - State: open - Opened by rodrigogiraudo about 5 years ago - 2 comments

#22 - Add @sentry/browser as a peer dependency or a range

Issue - State: open - Opened by darkowic about 5 years ago - 1 comment

#21 - fix: use semver in package.json dependencies

Pull Request - State: open - Opened by bradleyayers over 5 years ago - 2 comments

#20 - Error 'Sentry' is not defined no-undef

Issue - State: open - Opened by MatteoGioioso over 5 years ago - 5 comments

#19 - Important question

Issue - State: closed - Opened by whtcr almost 6 years ago - 16 comments

#18 - LogRocket integration?

Issue - State: open - Opened by bogdancss almost 6 years ago - 2 comments

#17 - Gatsby build produces error with webpack

Issue - State: open - Opened by stvnwrgs almost 6 years ago

#16 - Bad Sentry error messages

Issue - State: open - Opened by kievu almost 6 years ago

#15 - Replace require.ensure() with import()

Pull Request - State: open - Opened by antoinerousseau about 6 years ago - 4 comments

#14 - Action required: Greenkeeper could not be activated 🚨

Issue - State: open - Opened by greenkeeper[bot] about 6 years ago
Labels: greenkeeper

#13 - Extra gatsby-ssr.js file in npm package

Issue - State: closed - Opened by browniebroke about 6 years ago - 8 comments

#12 - Fixes typo

Pull Request - State: closed - Opened by schalkventer about 6 years ago - 1 comment

#11 - consider using latest SDK, Enabled based on environments from config

Pull Request - State: closed - Opened by mhadaily over 6 years ago - 7 comments

#10 - Only load Raven in production.

Pull Request - State: closed - Opened by octalmage over 6 years ago - 5 comments

#9 - Use script from NPM instead of CDN

Pull Request - State: closed - Opened by Thien42 over 6 years ago - 5 comments

#8 - docs: add `config` example

Pull Request - State: closed - Opened by bradleyayers almost 7 years ago

#7 - feat(dev): only add sentry plugin if node env is production

Pull Request - State: closed - Opened by roosnic1 almost 7 years ago - 3 comments

#6 - default ravenjs version is too old and does not stay up to date

Issue - State: closed - Opened by sedubois almost 7 years ago - 2 comments

#5 - Make script loading async?

Issue - State: closed - Opened by KyleAMathews about 7 years ago - 12 comments

#4 - Improve raven.js integration

Pull Request - State: closed - Opened by mickeyreiss-visor about 7 years ago - 3 comments

#3 - Feature: Disable in development environment

Issue - State: closed - Opened by benedfit about 7 years ago - 1 comment

#2 - Add missing keys.

Issue - State: closed - Opened by octalmage over 7 years ago - 1 comment
Labels: bug

#1 - Add release tracking.

Issue - State: closed - Opened by octalmage over 7 years ago - 5 comments
Labels: enhancement

Ecosyste.ms: Issues

GitHub / octalmage/gatsby-plugin-sentry issues and pull requests