Vue
If you're seeing deprecation warnings in your code, please note that we're currently working on version 8 of the JavaScript SDKs. In v8, some methods and properties will be removed or renamed. Check out the Migration docs and learn how to update your code to be compatible with v8.
Don't already have an account and Sentry project established? Head over to sentry.io, then return to this page.
Sentry captures data by using an SDK within your application’s runtime.
npm install --save @sentry/vue
Configuration should happen as early as possible in your application's lifecycle.
To initialize Sentry in your Vue application, add the following code snippet to your main.js
:
main.js
import {createApp} from 'vue';
import {createRouter} from 'vue-router';
import * as Sentry from '@sentry/vue';
const app = createApp({
// ...
});
const router = createRouter({
// ...
});
Sentry.init({
app,
dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0',
integrations: [Sentry.browserTracingIntegration({router}), Sentry.replayIntegration()],
// Set tracesSampleRate to 1.0 to capture 100%
// of transactions for performance monitoring.
// We recommend adjusting this value in production
tracesSampleRate: 1.0,
// Set `tracePropagationTargets` to control for which URLs distributed tracing should be enabled
tracePropagationTargets: ['localhost', /^https:\/\/yourserver\.io\/api/],
// Capture Replay for 10% of all sessions,
// plus for 100% of sessions with an error
replaysSessionSampleRate: 0.1,
replaysOnErrorSampleRate: 1.0,
});
app.use(router);
app.mount('#app');
main.js
import Vue from 'vue';
import Router from 'vue-router';
import * as Sentry from '@sentry/vue';
Vue.use(Router);
const router = new Router({
// ...
});
Sentry.init({
Vue,
dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0',
integrations: [Sentry.browserTracingIntegration({router}), Sentry.replayIntegration()],
// Set tracesSampleRate to 1.0 to capture 100%
// of transactions for performance monitoring.
// We recommend adjusting this value in production
tracesSampleRate: 1.0,
// Set `tracePropagationTargets` to control for which URLs distributed tracing should be enabled
tracePropagationTargets: ['localhost', /^https:\/\/yourserver\.io\/api/],
// Capture Replay for 10% of all sessions,
// plus for 100% of sessions with an error
replaysSessionSampleRate: 0.1,
replaysOnErrorSampleRate: 1.0,
});
// ...
new Vue({
router,
render: h => h(App),
}).$mount('#app');
If you're creating more than one Vue 3 app within your application, check out how to initialize the SDK for multiple apps.
The SDK accepts a few Vue-specific Sentry.init
configuration options:
attachProps
(defaults totrue
) - Includes all Vue components' props with the events.logErrors
(defaults totrue
) - Decides whether SDK should call Vue's originallogError
function as well.trackComponents
(defaults tofalse
) - Track your app's components. Learn more about component tracking and all its options.
Depending on how you've set up your project, the stack traces in your Sentry errors probably don't look like your actual code.
To fix this, upload your source maps to Sentry. The easiest way to do this is to use the Sentry Wizard:
npx @sentry/wizard@latest -i sourcemaps
The wizard will guide you through the following steps:
- Logging into Sentry and selecting a project
- Installing the necessary Sentry packages
- Configuring your build tool to generate and upload source maps
- Configuring your CI to upload source maps
For more information on source maps or for more options to upload them, head over to our Source Maps documentation.
This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.
Add a button to your page that throws an error:
App.vue
// ...
<button @click="throwError">Throw error</button>
// ...
export default {
// ...
methods: {
throwError() {
throw new Error('Sentry Error');
}
}
};
Learn more about manually capturing an error or message in our Usage documentation.
To view and resolve the recorded error, log into sentry.io and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").