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

@zzzen/sentry-webpack-plugin

v1.2.0

Published

Official webpack plugin for Sentry

Downloads

5

Readme

Travis codecov npm version npm dm npm dt

deps deps dev deps peer

A webpack plugin acting as an interface to Sentry CLI.

Installation

Using npm:

$ npm install @sentry/webpack-plugin --only=dev

Using yarn:

$ yarn add @sentry/webpack-plugin --dev

CLI Configuration

You can use either .sentryclirc file or ENV variables described here https://docs.sentry.io/learn/cli/configuration/

Usage

const SentryCliPlugin = require('@sentry/webpack-plugin');

const config = {
  plugins: [
    new SentryCliPlugin({
      include: '.',
      ignoreFile: '.sentrycliignore',
      ignore: ['node_modules', 'webpack.config.js'],
      configFile: 'sentry.properties',
    }),
  ],
};

Also, check the example directory.

Options

  • release [optional] - unique name of a release, must be a string, should uniquely identify your release, defaults to sentry-cli releases propose-version command which should always return the correct version
  • include [required] - string or array, one or more paths that Sentry CLI should scan recursively for sources. It will upload all .map files and match associated .js files
  • entries [optional] - array or RegExp or function(key: string): bool, a filter for entry points that should be processed. By default, the release will be injected into all entry points.
  • ignoreFile [optional] - string, path to a file containing list of files/directories to ignore. Can point to .gitignore or anything with same format
  • ignore [optional] - string or array, one or more paths to ignore during upload. Overrides entries in ignoreFile file. If neither ignoreFile or ignore are present, defaults to ['node_modules']
  • configFile [optional] - string, path to Sentry CLI config properties, as described in https://docs.sentry.io/learn/cli/configuration/#properties-files. By default, the config file is looked for upwards from the current path and defaults from ~/.sentryclirc are always loaded
  • ext [optional] - array, this sets the file extensions to be considered. By default the following file extensions are processed: js, map, jsbundle and bundle.
  • urlPrefix [optional] - string, this sets an URL prefix in front of all files. This defaults to ~/ but you might want to set this to the full URL. This is also useful if your files are stored in a sub folder. eg: url-prefix '~/static/js'
  • validate [optional] - boolean, this attempts sourcemap validation before upload when rewriting is not enabled. It will spot a variety of issues with source maps and cancel the upload if any are found. This is not the default as this can cause false positives.
  • stripPrefix [optional] - array, when paired with rewrite this will chop-off a prefix from uploaded files. For instance you can use this to remove a path that is build machine specific.
  • stripCommonPrefix [optional] - boolean, when paired with rewrite this will add ~ to the stripPrefix array.
  • sourceMapReference [optional] - boolean, this prevents the automatic detection of sourcemap references.
  • rewrite [optional] - boolean, enables rewriting of matching sourcemaps so that indexed maps are flattened and missing sources are inlined if possible., defaults to true
  • dryRun [optional] - boolean, attempts a dry run (useful for dev environments)
  • debug [optional] - boolean, print some useful debug information

You can find more information about these options in our official docs: https://docs.sentry.io/learn/cli/releases/#upload-source-maps