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

@appsignal/webpack

v1.1.6

Published

- [AppSignal.com website][appsignal] - [Documentation][docs] - [Support][contact]

Downloads

1,539

Readme

@appsignal/webpack

The @appsignal/javascript integration for Webpack v4+.

⚠️ The Webpack plugin is currently in BETA. Please report any bugs to us here, your feedback is appreciated.

Installation

Add the @appsignal/webpack packages to your package.json. Then, run yarn install/npm install.

You can also add these packages to your package.json on the command line:

yarn add @appsignal/webpack
npm install --save @appsignal/webpack

Usage

AppsignalPlugin

In a new or existing Webpack-based app, your webpack.config.js file would include something like this:

const { AppsignalPlugin } = require("@appsignal/webpack")

const config = {
  // ...other config here
  plugins: [
    // ...other plugins here (optional)
    new AppsignalPlugin({
      // required
      apiKey: "<your Push API key (NOT your frontend key!)>",
      release: "<a valid Git SHA>",
      appName: "<the app name as it appears on AppSignal.com>",
      environment: "<the current environment>",
      urlRoot: "<the root URL where your sourcemaps are held>" | ["<an array of root URLs>"]

      // not required
      deleteAfterCompile: true | false, // OPTIONAL: cleanup sourcemap files after upload
      timeout: 5000 // OPTIONAL: increase max timeout of http client
    })
  ],
  devtool: "source-map"
}

module.exports = config

Development

Installation

This repository is a Lerna-managed monorepo, containing packages (located in the /packages directory) that map to separate npm modules.

To install the dependencies:

yarn install
lerna bootstrap

You can then run the following to start the compiler in watch mode. This automatically compiles both the ES Module and CommonJS variants:

yarn build:watch

You can also build the library without watching the directory:

yarn build        # build both CJS and ESM
yarn build:cjs    # just CJS
yarn build:esm    # just ESM

Testing

The tests for this library use Jest as the test runner. Once you've installed the dependencies, you can run the following command in the root of this repository to run the tests for all packages, or in the directory of a package to run only the tests pertaining to that package:

yarn test

Versioning

This repo uses Semantic Versioning (often referred to as semver). Each package in the repository is versioned independently from one another.

@TODO: define how this works once we know more about releasing

Contributing

Thinking of contributing to this repo? Awesome! 🚀

Please follow our Contributing guide in our documentation and follow our Code of Conduct.

Also, we would be very happy to send you Stroopwafles. Have look at everyone we send a package to so far on our Stroopwafles page.

Support

Contact us and speak directly with the engineers working on AppSignal. They will help you get set up, tweak your code and make sure you get the most out of using AppSignal.