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

@raygun.io/webpack-plugin

v0.1.0

Published

A Webpack plugin for automating uploading your source maps to Raygun

Downloads

125

Readme

Raygun Webpack Plugin

The Raygun Webpack plugin automatically detects sourcemaps generated during your builds and sends them to Raygun, facilitating better error diagnostics by mapping minified code back to your original source code.

Installation

Npm:

npm install @raygun/webpack-plugin

Yarn:

yarn add @raygun/webpack-plugin

Bun:

bun install @raygun/webpack-plugin

Usage

const RaygunWebpackPlugin = require('raygun-webpack-plugin');

module.exports = {
    // Your existing webpack config...
    plugins: [
        new RaygunWebpackPlugin({
            baseUri: 'YOUR_WEBSITE_BASE_URI', 
            applicationId: 'YOUR_APPLICATION_ID',
            patToken: 'YOUR_PAT_TOKEN',
        })
    ]
};

Configuration Options

  • baseUri (required): Specifies the base URI for your website E.g. http://localhost:3000/.
  • applicationId (required): Your Raygun application identifier.
  • patToken (required): Your Raygun Personal Access Token with Sourcemap write permissions. Can be generated here: https://app.raygun.com/user/tokens

How it works

Raygun looks for sourcemaps based on the url for the .js file where the error occored, when you upload a sourcemap you must also provide that url as a key for the map file. The plugin - using your base URI - will find all built sourcemaps and will attempt to construct the URL based on the build directory.

Building

npm run build

Support

For support with the Raygun Webpack Plugin, please open an issue in our GitHub repository.