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

spill-netlify-build-plugin

v1.2.1

Published

The Sentry Netlify build plugin automatically uploads source maps and notifies Sentry of new releases being deployed to your site after it finishes building in Netlify.

Downloads

5

Readme

Sentry Netlify build plugin    

Automatically upload source maps and notify Sentry of new releases being deployed to your site after it finishes building in Netlify.

The Sentry Netlify build plugin:

  • Notifies Sentry of new releases being deployed.
  • Uploads source maps to Sentry.
  • Sends Sentry the commit SHA of HEAD to enable commit features.

Before proceeding, you'll first want to ensure that your Sentry project is set up properly to track commit metadata. The easiest way to do that is to install a repository integration.

By default, the linked Sentry repository will be parsed from the Netlify's REPOSITORY_URL environment variable. This behaviour can be overridden using the SENTRY_REPOSITORY environment variable.

Make sure build plugins are enabled on your site to see the plugin run.

Installation

UI Installation

To install plugins via the Netlify UI, go to your team sites list and select the Plugins tab (or follow this direct link to the plugins directory). Then find "Sentry Build Plugin" and click Install.

UI installation is the recommended way to install this Build Plugin unless you need advanced configuration.

File-based Installation

Alternatively, to install with file-based installation, add the following lines to your netlify.toml file:

[[plugins]]
  package = "@sentry/netlify-build-plugin"

  [plugins.inputs]
    sentryOrg = ""
    sentryProject = ""

Note: The [[plugins]] line is required for each plugin installed via file-based installation, even if you have other plugins in your netlify.toml file already.

Create a Sentry Internal Integration

For Netlify to communicate securely with Sentry, you'll need to create a new internal integration. In Sentry, navigate to: Settings > Developer Settings > New Internal Integration.

Give your new integration a name (for example, “Netlify Deploy Integration”) and specify the necessary permissions. In this case, we need Admin access for “Release” and Read access for “Organization”.

View of internal integration permissions.

Click “Save” at the bottom of the page and grab your token, which you’ll need this in the next step.

Set Environment Variables in Netlify

Save the internal integration token and any other environment variables as site environment variables:

  1. In Netlify, go to your site's settings.
  2. Click on "Build & deploy".
  3. Click “Edit variables” and add SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT with their respective values. For more configuration options see the environment variables section below.
  4. Click "Save".

View of internal integration permissions.

For more information about the parameters below, please see the Sentry release management docs.

Ensure Your SDK is Configured

To link errors with releases, you must include a release ID (a.k.a version) where you configure your client SDK. For more information, read our documentation on configuring your SDK for releases.

Environment Variables

You can use site environment variables to configure these values: | name | description | default | | ----------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------- | | SENTRY_AUTH_TOKEN | Authentication token for Sentry. | - | | SENTRY_ORG | The slug of the organization name in Sentry. | - | | SENTRY_PROJECT | The slug of the project name in Sentry. | - | | SENTRY_RELEASE | The release ID (a.k.a version). | COMMIT_REF | | SENTRY_REPOSITORY | The name of the target Sentry repository. | - | | SENTRY_ENVIRONMENT | The name of the environment being deployed to. | Netlify deploy context | | SENTRY_RELEASE_PREFIX | Set this to prefix the release name with the value. | - |

Plugin Inputs

| name | description | default | | -------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | sentryOrg | The slug of the organization name in Sentry. | - | | sentryProject | The slug of the project name in Sentry. | - | | sentryAuthToken | Authentication token for Sentry. We recommend this be set as an environment variable (see below). | - | | sentryRelease | The release ID (a.k.a version). | COMMIT_REF | | sentryRepository | The name of the target Sentry repository. | Derived from REPOSITORY_URL | | sourceMapPath | Folder in which to scan for source maps to upload. | Netlify publish directory | | sourceMapUrlPrefix | Prefix for the location of source maps. | "~/" | | skipSetCommits | Set this to true if you want to disable commit tracking. | false | | skipSourceMaps | Set this to true if you want to disable sending source maps to Sentry. | false | | releasePrefix | Set this to prefix the release name with the value. | - | | deployPreviews | Set this to false if you want to skip running the build plugin on deploy previews. | true | | sentryDeleteSourceMaps | Set this to true if you to delete sourcemaps after they have been sent to Sentry. | false |