Skip to content

Definitive guide to Sourcemaps and more with Sveltekit 🎉 #43301

Closed
@alexbjorlig

Description

@alexbjorlig

Problem Statement

SvelteKit is awesome - and it's now version 1 (fresh out of beta)!

One of the great things about SvelteKit is the ability to abstract away the hosting provider. You write the same code, and then you can use an adapter to deploy where you want. It could be

  • Node.js platforms like Heroku
  • Cloudflare edge functions
  • Vercel
  • Netlify

The good question now is: How do we get source maps to Sentry?
And follow-ups like:

  • Should you setup both @sentry/browser @sentry/node?
  • Is it wise to use both server/client error hooks?
  • Where do you hook into the Sveltekit life-cycle to enrich the sentry scope on the server?
  • What breadcrumbs do you recommend removing from the default setup?

It would be such a cool thing to solve ❤️ (Sveltekit actually mentions Sentry already in certain places in the docs).

Solution Brainstorm

I guess the first path to a more robust solution, would be documentation about how sourcemaps can be synced for the different adapters (if there is any change at all???)

Ultimately an integration with the Sentry CLI would be 🥷

Let me know what you think? - How do you sync source maps from a Sveltekit project?

Our team has not done it yet 🫣

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions