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

profiler-sourcemap-injector

v1.0.0

Published

Injects sourcemaps into .cpuprofile files

Downloads

17

Readme

Profiler sourcemap injector

This package injects source map files into .cpuprofile files generated by Chrome DevTools.

Installation

npm install profiler-sourcemap-injector

or

yarn add profiler-sourcemap-injector

Usage

import { injectSourceMaps } from 'profiler-sourcemap-injector';

const outputObject = await injectSourceMaps('path/to/profile.cpuprofile', 'path/to/output/profile.cpuprofile', {
    sourceMapDir: 'path/to/source/maps', // Directory where source maps are located
    sourceDir: 'path/to/source/files', // Optional path to source file directory
    profileSourceRoot: 'root/of/profile/source/paths', // Optional root path of source paths in .cpuprofile file
    
    log: (msg) => console.log(msg), // Optional logging function
    transformSource: (path) => path, // Optional function to transform source paths
    sourceMapProvider: (path) => null, // Optional function to provide source maps
});

.cpuprofile reading

You can specify JSON-parsed .cpuprofile object instead of file path.

Path resolution

If profileSourceRoot is specified, the speicfied value will be removed from the start of each .cpuprofile path.
If sourceDir is specified, the specified value will be appended to the start of each .cpuprofile path.
This is helpful if you want to forcefully resolve paths to use in e.g. VSCode

You can override that behavior by specifying transformSource function. The function gets .cpuprofile path as an input, and outputs new path.

Source map reading

By default this package reads source maps from the sourceMapDir, looking for files with the same name as .js, but with .map extension.
You can override that behavior by specifying sourceMapProvider function. The function gets .cpuprofile path as an input, and outputs source map contents string.

Usage outside of NodeJS environment

To use this module outside of NodeJS you can override sourceMapProvider function, provide profile object instead of .cpuprofile path, and specify null to the output argument. You can get resulting profile object from the return value of the function.

License

MIT

Contributions

PRs are very welcome!