grunt-external-sourcemap

Extracts sourcemaps from a js file and links the original file to an external source map file

Getting Started

This plugin requires Grunt ~0.4.1

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-external-sourcemap --save-dev

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

grunt.loadNpmTasks('grunt-external-sourcemap');

The "external_sourcemap" task

Overview

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

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

Usage Examples

Default Options

Given a set of files with inline source maps, the source maps are extracted into their own files and the original .js files are updated to point at the new external source map file.

grunt.initConfig({
  external_sourcemap: {
    files: {
      'public/build': ['src/build/output1.js', 'src/build/output2.js'],
    },
  },
})

Custom Options

You set a flag, removeSourcesContent, which will remove the sourcesContent field from the extracted source map.

grunt.initConfig({
  external_sourcemap: {
    options: { 'removeSourcesContent': true }
    files: {
      'public/build': ['src/build/output1.js', 'src/build/output2.js'],
    },
  },
})

Installation

$ npm install grunt-external-sourcemap

Tests

$ npm test