> Grunt task for Chrome manifest.json
Grunt task for Chrome manifest.json
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, install this plugin with this command:
npm install grunt-chrome-manifest --save-dev
chrome-manifest is composed of 3 steps:
buildnumberand increased if set to true.
chromeManifest:dist:options:buildnumber: 'both'background:target: 'scripts/background.js'exclude:'background/scripts/chromereload.js'src: 'app'dest: 'dist'manifest: 'app/manifest.json';
Base directory where the origin source files
Base directory where the transformed files should be output.
Path of the source of
manifest.json. If it's not set the plugin will be going to read
Auto-increment types. Can be:
dest: increase build number in dest only
both: increase build number in both origin and dest
String: version in this format
false: do not increase build number
String, Relative path of the transformed(
uglify) background script.
Overwrite in manifest keys from object.
Remove fields from manifest.json. The key field is removed by default as it is not allowed by the chrome webstore.
Grunt currently doesn't have a way to test tasks directly. You can test this task by running
grunt and manually verify that it works.
BSD license and copyright Google