npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@gambalabs/sentry-nuxt

v8.32.0

Published

Official Sentry SDK for Nuxt (EXPERIMENTAL)

Downloads

963

Readme

Official Sentry SDK for Nuxt (EXPERIMENTAL)

npm version npm dm npm dt

This SDK is under active development! Feel free to already try it but expect breaking changes

Links

todo: link official SDK docs

Compatibility

The minimum supported version of Nuxt is 3.0.0.

General

This package is a wrapper around @sentry/node for the server and @sentry/vue for the client side, with added functionality related to Nuxt.

What is working:

  • Error Reporting
    • Vue
    • Node
    • Nitro

What is partly working:

  • Source Maps
  • Connected Tracing (Frontend & Backend)
  • Tracing by setting tracesSampleRate
    • UI (Vue) traces
    • HTTP (Node) traces

Known Issues:

  • When adding sentry.server.config.(ts/js), you get an error like this: "Failed to register ESM hook (import-in-the-middle/hook.mjs)". You can add a resolution for @vercel/nft to fix this. This will add the hook.mjs file to your build output (issue here).
      "resolutions": {
        "@vercel/nft": "^0.27.4"
      }

Automatic Setup

todo: add wizard instructions

Take a look at the sections below if you want to customize your SDK configuration.

Manual Setup

If the setup through the wizard doesn't work for you, you can also set up the SDK manually.

1. Prerequisites & Installation

  1. Install the Sentry Nuxt SDK:

    # Using npm
    npm install @sentry/nuxt
    
    # Using yarn
    yarn add @sentry/nuxt

2. Nuxt Module Setup

The Sentry Nuxt SDK is based on Nuxt Modules.

  1. Add @sentry/nuxt/module to the modules section of nuxt.config.ts:
// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@sentry/nuxt/module'],
});

3. Client-side setup

Add a sentry.client.config.(js|ts) file to the root of your project:

import { useRuntimeConfig } from '#imports';
import * as Sentry from '@sentry/nuxt';

Sentry.init({
  // If set up, you can use your runtime config here
  dsn: useRuntimeConfig().public.sentry.dsn,
});

4. Server-side setup

Add an sentry.client.config.(js|ts) file to the root of your project:

import * as Sentry from '@sentry/nuxt';

// Only run `init` when process.env.SENTRY_DSN is available.
if (process.env.SENTRY_DSN) {
  Sentry.init({
    dsn: 'your-dsn',
  });
}

The Nuxt runtime config does not work in the Sentry server to technical reasons (it has to be loaded before Nuxt is loaded). To be able to use process.env you either have to add --env-file=.env to your node command

node --env-file=.env --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs

or use the dotenv package:

import dotenv from 'dotenv';
import * as Sentry from '@sentry/nuxt';

dotenv.config();

Sentry.init({
  dsn: process.env.SENTRY_DSN,
});

Add an import flag to the Node options of your node command (not nuxt preview), so the file loads before any other imports (keep in mind the .mjs file ending):

{
  "scripts": {
    "start": "node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs"
  }
}

Uploading Source Maps

To upload source maps, you can use the sourceMapsUploadOptions option inside the sentry options of your nuxt.config.ts:

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@sentry/nuxt/module'],
  sentry: {
    debug: true,
    sourceMapsUploadOptions: {
      org: 'your-org-slug',
      project: 'your-project-slug',
      authToken: process.env.SENTRY_AUTH_TOKEN,
    },
  },
});