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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fernando.mema/sv-sentry

v0.1.1

Published

<a id="readme-top"></a>

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

fernandomemafernandomema

Keywords

sv-addsveltesveltekitsentryerror-trackingmonitoring

Readme

NPM Version MIT License Svelte CLI

View Sentry Docs · Report Bug · Request Feature

About

This addon sets up Sentry in your SvelteKit project with:

  • Browser-side error tracking
  • Server-side error tracking
  • Session replay support
  • Source map upload configuration
  • Vite plugin integration

Installation

npx sv add @fernandomema/sv-sentry

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | browser | boolean | true | Enable Sentry for browser (client-side) | | server | boolean | true | Enable Sentry for server (server-side) | | replays | boolean | false | Enable Session Replays (browser only) |

What It Does

Files Created

| File | Purpose | |------|---------| | src/lib/sentry.client.ts | Browser-side Sentry initialization | | src/lib/sentry.server.ts | Server-side Sentry initialization | | sentry.client.config.ts | Client config (if server enabled) | | sentry.server.config.ts | Server config (if server enabled) |

Files Modified

| File | Changes | |------|---------| | .env | Adds PUBLIC_SENTRY_DSN, SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT | | .env.example | Adds environment variable templates | | src/hooks.server.ts | Adds Sentry server handle | | src/hooks.client.ts | Adds client-side Sentry import | | vite.config.ts | Adds Sentry Vite plugin (if server enabled) | | package.json | Adds sentry:sourcemaps script |

Environment Variables

| Variable | Description | |----------|-------------| | PUBLIC_SENTRY_DSN | Sentry DSN for client-side error tracking | | SENTRY_AUTH_TOKEN | Sentry auth token for source maps upload | | SENTRY_ORG | Sentry organization slug | | SENTRY_PROJECT | Sentry project slug |

Next Steps

After installation:

  1. Set PUBLIC_SENTRY_DSN in .env
  2. Set SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT in .env
  3. Run npm run sentry:sourcemaps to upload source maps after building
  4. If Session Replays enabled, check Sentry dashboard for recordings

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE.txt for more information.

Contact

Fernando - @fernandomema

Project Link: https://github.com/fernandomema/sv-addons

Acknowledgments