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 🙏

© 2026 – Pkg Stats / Ryan Hefner

join-source-map

v1.0.0

Published

Merge the SourceMap files generated in several steps, and overwrite the last one with the merged one.

Downloads

10

Readme

join-source-map

join-source-map npm version

Merge the SourceMap files generated in several steps, and overwrite the last one with the merged one.

What problems do I aim to solve?

We usually process the TypeScript code with many tools in pipelines, many of them may generate SourceMap files for debugging use, but these SourceMap files are mapped to the files generated in the previous step, not the original one. Several npm packages are aiming to solve this problem, as I tried, the best working one is multi-stage-sourcemap, however, it just processes only two SourceMap files each time, you need to figure out which two - not very friendly for batch processing, another problem is it does not support the "bundled" SourceMap, which means it has more than one sources. The join-source-map is designed to batch process all the SourceMap files in a folder in a very efficient way, it automatically traces up through the SourceMap chain collecting information, but only overwrites the very last one. Also, it supports the bundled SourceMap files.

Install

install as a dev dependency and run with npx join-source-map

npm install --save-dev join-source-map

or install it globally and run with command join-source-map

npm install -g join-source-map

Important:

  • Make sure all the generated files with SourceMaps have a link line (//# sourceMappingURL=xxx.map) pointing to the relevant .map file. The mergeSourceMap feature depends on it to trace up the SouceMap chains.

  • Currently join-source-map does not support inline SourceMaps.

Command line usage

To show the usage: npx join-source-map -h

Usage: join-source-map [options] <out-dir> <file-exts...>

Merge all the relevent SourceMap files of files with specific extentions in a folder.

Arguments:
  out-dir         the output folder path
  file-exts       the file extentions, like .js or .d.ts, also
                  accept .map

Options:
  -r --recursive  loop through all sub directories
  -h, --help      display help for command

Thanks to

source-map

multi-stage-sourcemap