Skip to content

Move Browserify source maps to a separate file using Exorcist and Grunt

License

Notifications You must be signed in to change notification settings

ApelegHQ/grunt-exorcise

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

grunt-exorcise Travis CI

Move Browserify source maps to a separate file using Exorcist and Grunt

Getting Started

This plugin requires Grunt 0.4.x

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-exorcise --save-dev

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

grunt.loadNpmTasks('grunt-exorcise');

The "exorcise" task

grunt.initConfig({
  exorcise: {
    bundle: {
      options: {},
      files: {
        'public/js/bundle.map': ['public/js/bundle.js'],
      }
    }
  }
});

Options

options.bundleDest

Type: String

Location to place the new bundle with the inline source map removed. By default the source bundle file will be overwritten.

options.strict

Type: Boolean Default: false Fail the build when the source map is missing. Default is false, equivalent to exorcist default behaviour.

options.url & options.root & options.base

Type: String

Passed directly to exorcist. Refer to the exorcist documentation.

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

v0.1.0

  • Initial release

About

Move Browserify source maps to a separate file using Exorcist and Grunt

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 100.0%