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

grunt-multi-stage-sourcemap

v0.1.0

Published

Remap multi-level sourcemaps

Downloads

4

Readme

grunt-multi-stage-sourcemap Build Status

Remap multi-level sourcemaps using the multi-stage-sourcemap library.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-multi-stage-sourcemap --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-multi-stage-sourcemap');

The "multi_stage_sourcemap" task

Overview

In your project's Gruntfile, add a section named multi_stage_sourcemap to the data object passed into grunt.initConfig().

grunt.initConfig({
  multi_stage_sourcemap: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.map

Type: function

Default value:

function naiveMapping(pathMapFrom, pathMapTo) {

  function getFilename(path) {
    return path.split("/").pop();
  }

  if (getFilename(pathMapFrom) === getFilename(pathMapTo)) {
    return true;
  }
}

A function which decides which maps should be offset to each other. The function recieves the paths to both files and should return true if they match up otherwise it should return false.

By default the function will return true if both files have the same name.

Usage Examples

Default Options

In this example, the default options are used to retrieve the default_options.js.map source map from directory A and remap it using default_options.js.map from directory B.

grunt.initConfig({
  multi_stage_sourcemap: {
    filesFrom: 'test/fixtures/A/default_options.js.map',
    options: {},
    files: [{
      expand: true,
      cwd: 'test/fixtures/B/',
      src: ['default_options.js.map'],
      dest: 'tmp'
    }],
  },
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • Nov 7, 2014 - v0.1.0