npmpackage.info

Gathering detailed insights and metrics for @pdga-technology/vite-plugin-bugsnag

@pdga-technology/vite-plugin-bugsnag - 2.0.2 | npmpackage.info

@pdga-technology/vite-plugin-bugsnag

Report builds and upload source maps to Bugsnag

2.0.2

MIT

TypeScript

22.32 kB

2.6

Installations

npm install @pdga-technology/vite-plugin-bugsnag

Developer Guide

BETA

Typescript

Yes

Module System

ESM

Node Version

14.15.4

NPM Version

8.7.0 Pull Requests

Open

1

Total

3

Closed

0

Merged

2

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Languages

TypeScript

JavaScript

Shell

TypeScript (77.24%)

JavaScript (22.18%)

Shell (0.58%)

Developer

ElMassimo

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

22 Stars

20 Commits

6 Forks

2 Watchers

1 Branches

4 Contributors

Updated on Jun 13, 2025

Maintainers

View All 4 Contributors

Package Meta Information

Latest Version

2.0.2

Package Id

@pdga-technology/vite-plugin-bugsnag@2.0.2

Unpacked Size

22.32 kB

Size

6.61 kB

File Count

NPM Version

8.7.0

Node Version

14.15.4

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@bugsnag/source-maps bugsnag-build-reporter debug fast-glob p-limit picocolors

Peer Dependencies

vite

Dev Dependencies

`vite-plugin-bugsnag`

Report builds and upload source maps to bugsnag

Why? 🤔

There is no official plugin from Bugsnag for Vite.js.

This plugin provides the same functionality as webpack-bugsnag-plugins in Vite.js.

The API is similar to simplify the migration when moving away from Webpack.

Features ⚡️

🔒 Written in TypeScript
🚀 Quick setup with Vite plugins
📖 Config options are fully documented in JSDoc

Installation 💿

Install the package as a development dependency:

1npm i -D vite-plugin-bugsnag # yarn add -D vite-plugin-bugsnag

Usage 🚀

Two plugins are provided, one to report build information, and another one to upload sourcemaps.

Both plugins accept apiKey, appVersion, and endpoint, so you can share a config object.

For example:

1import { defineConfig } from 'vite'
2import { BugsnagBuildReporterPlugin, BugsnagSourceMapUploaderPlugin } from 'vite-plugin-bugsnag'
3
4const isDistEnv = process.env.RAILS_ENV === 'production'
5
6const bugsnagOptions = {
7  apiKey: process.env.BUGSNAG_API_KEY,
8  appVersion: process.env.APP_VERSION,
9}
10
11export default defineConfig({
12  plugins: [
13    isDistEnv && BugsnagBuildReporterPlugin({ ...bugsnagOptions, releaseStage: process.env.RAILS_ENV }),
14    isDistEnv && BugsnagSourceMapUploaderPlugin({ ...bugsnagOptions, overwrite: true }),
15  ],
16})

`BugsnagBuildReporterPlugin (options)`

Use this plugin to report your application's build to Bugsnag.

1import { defineConfig } from 'vite'
2import { BugsnagBuildReporterPlugin } from 'vite-plugin-bugsnag'
3
4export default defineConfig({
5  plugins: [
6    BugsnagBuildReporterPlugin({
7      apiKey: 'YOUR_API_KEY',
8      appVersion: '1.2.3',
9    }),
10  ],
11})

It can auto detect source control from .git, .hg and package.json
Hooks into writeBundle to upload the information once the build is finished
If the build fails, the build report will not be sent

`BugsnagSourceMapUploaderPlugin (options)`

Use this plugin to upload your application's sourcemaps to Bugsnag.

1import { defineConfig } from 'vite'
2import { BugsnagSourceMapUploaderPlugin } from 'vite-plugin-bugsnag'
3
4export default defineConfig({
5  build: {
6    sourcemap: true,
7  },
8  plugins: [
9    BugsnagSourceMapUploaderPlugin({
10      apiKey: 'YOUR_API_KEY',
11      appVersion: '1.2.3',
12      base: 'https://your-app.xyz/assets/',
13    }),
14  ],
15})

The plugin will enable build.sourcemap in order for Vite to generate sourcemaps
It will upload any generated sourcemaps to Bugsnag

License

This library is available as open source under the terms of the MIT License.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.6

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More