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

source-map-compactor

v1.0.1

Published

Compacts sourcemaps, merging spurious mappings.

Downloads

2,177

Readme

source-map-compactor

Compacts sourcemaps, merging spurious mappings.

Rationale

I love Rollup. I really do.

But.

Sometimes the sourcemaps look crazy, and make my browser choke on them, confuse variable scopes, prevent setting breakpoints, and generally misbehave.

This is due to the way magic-string handles sourcemap mappings.

To remedy that, source-map-compactor looks at a sourcemap and performs four naïve optimizations:

  • Inserts blank line mappings when there is no mapping for a generated line.
  • Inserts blank character mappings at column 0 if there is no mapping for column 0 in a generated line.
  • Removes duplicated mappings to the same generated line-column (happens when magic-string replaces something with an empty string)
  • Removes duplicated mappings for contiguous segments of the same length (happens when magic-string copies several tokens in succesion)

These optimizations are not exhaustive, but they should create simpler and more reliable sourcemaps in most workflows.

Demo

The optimizations are easier to see with something like source-map-visualization:

Before:

Sourcemap visualization before

After:

Sourcemap visualization after

Usage

Install it from NPM:

yarn add source-map-compactor

In JS, require it and call it. It expects a string representing the sourcemap JSON, and returns a string representing a sourcemap JSON.

var compactor = require('source-map-compactor');
var fs = require('fs');

var sourceMapText = fs.readFileSync('bundle.js.map').toString();
var compactedSourceMapText = compactor(sourceMapText);
fs.writeFileSync('bundle.js.map', compactedSourceMap);

In a shell, run source-map-compactor with the filenames for input and output files, e.g.:

./node_modules/source-map-compactor build/bundle.js.map build/bundle.js.compacted.map

License

"THE BEER-WARE LICENSE": [email protected] wrote this file. As long as you retain this notice you can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return.