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

backtrace-sourcemap-tools

v0.1.1

Published

A collection of tools easing SourceMap handlng.

Downloads

3

Readme

backtrace-sourcemap-tools

Backtrace helper for adding Source Maps support to error reporting.

Usage

Add dev dependency

  "devDependencies": {
    "backtrace-sourcemap-tools": "[email protected]:backtrace-labs/backtrace-sourcemap-tools.git"
  }

Add Backtrace options

The upload URL is necessary as well as the list of map files to be uploaded.

Note: the token here is the symbol upload token, not the error reporting token.

Note: SYMBOLICATION_ID will be replaced by the uploader script with the correct value.

  "backtrace": {
    "sourcemap": {
      "upload": "https://<universe>.sp.backtrace.io:6098/post?format=sourcemap&token=<token>&project=<project>&universe=<universe>"
    },

Set up sourcemaps upload

There are two ways of doing this.

Upload all artifact .map files

Use backtrace-sourcemap with action upload and parameters package.json and the build folder (in the example: ./dist):

    "build": "my current build command && npm run upload",
    "upload": "./node_modules/.bin/backtrace-sourcemap upload package.json dist",

Set up automatic UUID generation in backtrace-node

var client = bt.initialize({
  endpoint: '...',
  token: '...'
});
client.setSymbolication(); // this line enables automatic UUID generation

Upload specific files

Add files to be uploaded to the .backtrace.sourcemap node in package.json.
  "backtrace": {
    "sourcemap": {
      "files": [
        "dist/bundle.js.map"
      ],
    },
Add GUID generation build scripts (optional)

This step is optional, but recommended for readability.

    "generate-uuids": "npx backtrace-sourcemap generate-uuids package.json src/backtrace_uuid.js",
    "upload": "npx backtrace-sourcemap upload-sourcemaps package.json src/backtrace_uuid.js",
Add the generated attribute to the report
const backtrace_uuid = require('../backtrace_uuid');

// ...

const uuid = await backtrace_uuid.getBacktraceUuid();
backtrace.reportSync(error, { symbolication_id: uuid });