Skip to content
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

Uncaught TypeError: o.Offline is not a constructor #2868

Closed
6 of 7 tasks
nwaughachukwuma opened this issue Aug 31, 2020 · 6 comments · Fixed by #3508
Closed
6 of 7 tasks

Uncaught TypeError: o.Offline is not a constructor #2868

nwaughachukwuma opened this issue Aug 31, 2020 · 6 comments · Fixed by #3508

Comments

@nwaughachukwuma
Copy link

nwaughachukwuma commented Aug 31, 2020

Package + Version

  • @sentry/browser
  • Sentry Integration
  • @sentry/node

Version:

5.22.3

Description

Based on the new offline feature done in #2778 I tried to add the Sentry Offline integration to our project and got the following error

Uncaught TypeError: o.Offline is not a constructor
    at Module.cd49 (sentry.ts:17)
    at s (bootstrap:84)
    at Object.0 (app.be676346.js:1)
    at s (bootstrap:84)
    at n (bootstrap:45)
    at bootstrap:221
    at app.be676346.js:1

Describe your issue in detail, ideally, you have a reproducible demo that you can show.

import Vue from 'vue'
import * as Sentry from '@sentry/browser'
import { Vue as VueIntegration, Offline } from '@sentry/integrations'

Sentry.init({
  release: 'release_v',
  environment: 'release_env',
  dsn: 'SENTRY_DSN',
  enabled: true,
  integrations: [
    new VueIntegration({
      Vue,
      attachProps: true,
      logErrors: true,
    }),
    new Offline(),
  ],
})
@nwaughachukwuma
Copy link
Author

Did I initialize this the wrong way? @voraciousdev @AbhiPrasad

@davidmyersdev
Copy link
Contributor

davidmyersdev commented Sep 1, 2020

There was a reason I wrote the import the way I did in the PR. I'm guessing it has to do with one of these changes.

@nwaughachukwuma
Copy link
Author

There was a reason I wrote the import the way I did in the PR. I'm guessing it has to do with one of these changes.

Ok cool. Please what's the best way to add this integration?

@davidmyersdev
Copy link
Contributor

@nwaughachukwuma I imagine using version 5.22.0 would work (that's the version I'm currently using in my own project).

@lobsterkatie
Copy link
Member

@nwaughachukwuma - once #3508 is released (should be in the next few days), can you please let us know if you're still having the above problems? I'm going to close this, because I believe it's fixed, but do please give us a heads-up if you discover it's not.

@davidmyersdev
Copy link
Contributor

I can test this once the release is out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants