JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 337
  • Score
    100M100P100Q96331F
  • License MIT

Browser library to report errors to GCP

Package Exports

  • @apolitical/error-reporting
  • @apolitical/error-reporting/build/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@apolitical/error-reporting) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Apolitical Error Reporting

Browser (and Node.js) library to report errors to GCP

Requirements

Requires the following to run:

Installation

Install with yarn:

yarn add @apolitical/error-reporting

Available Scripts

In the project directory, you can run:

yarn run test

Runs the test (and the interactive mode can be enabled with --watchAll).

yarn build

Builds the library for production to the build folder. It correctly bundles the code on production mode and optimizes the build for the best performance.

yarn publish

Publishes the library to NPM.

Usage

The recommended way to use @apolitical/error-reporting is to set the context with the appropriate parameters:

const { setContext, reportError } = require('@apolitical/error-reporting');

setContext({
  origin: 'some-url',
  accessToken: 'some-token',
  serviceName: 'some-service'
});

And then, you can report the error to GCP like this:

await reportError(new Error('Something went wrong'));