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

@salesforce-sentry/codemods

v1.0.1

Published

CLI to adopt the salesforce-sentry SDK in an SFDX project

Vulnerabilities

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

Links

Maintainers

gaelmottegaelmotte

Keywords

Readme

@salesforce-sentry/codemods

CLI to adopt the salesforce-sentry SDK in an SFDX project.

Installation

npm install -g @salesforce-sentry/codemods

Or run without installing via npx:

npx @salesforce-sentry/codemods <command>

Commands

All commands accept an optional path to the SFDX project root. Defaults to the current working directory.

setup

Interactive wizard that generates the files needed to wire up the SDK:

  • An Apex config class extending sentrysdk.SentryConfig
  • Its .cls-meta.xml
  • A sentrysdk__Sentry_Config.Default.md-meta.xml custom metadata record
  • A Sentry.remoteSite-meta.xml remote site setting
salesforce-sentry setup [project-path]

You will be prompted for:

  • DSN — your Sentry project DSN (https://<key>@<host>/<projectId>)
  • Apex class name — defaults to MySentryConfig
  • Sampling rate — 0–100, defaults to 100
  • Integrations — multiselect from all available integrations

Generated files are written to the default package directory from sfdx-project.json. Deploy them with sf project deploy start.

adopt

Scans your SFDX project and instruments LWC components and Apex entry points with Sentry error capture. Shows a diff for each file and prompts before applying.

salesforce-sentry adopt [project-path]

LWC components:

  • Exposed components (isExposed: true) → wrapped with SentryBoundaryMixin
  • Other components → wrapped with SentryMixin

Apex entry points instrumented:

  • @AuraEnabled methods → try/catch with captureException + AuraHandledException
  • @InvocableMethod, @RemoteAction, @HttpGet/Post/Put/Delete/Patch → try/catch with captureException + rethrow
  • Schedulable.execute, Queueable.execute, Database.Batchable start/execute/finish → same

Already-instrumented files are skipped automatically.

validate

Checks that the SDK is correctly wired up in the project:

salesforce-sentry validate [project-path]

Verifies:

  • sfdx-project.json exists
  • Exactly one Sentry_Config metadata record is enabled
  • DSN is set and valid
  • Remote site setting matches the DSN host
  • Apex config class exists on disk
  • No uninstrumented LWC or Apex entry points remain