A simple phantom.js based snapshots creator for single page applications written in Angular 1.x. DO NOT use it for regular website (whose front-end works not in Angular 1.x) with default phantom.js job. In case if you DO want to use it for regular website you have to set path to phantom.js job (see details bellow). This plugin will successfully create a page snapshot if it has automatically bootstrapped module (marked with either ng-app, or data-ng-app, or x-ng-app, or ng_app attribute).
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-ng-html-snapshot --saveOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-ng-html-snapshot');In your project's Gruntfile, add a section named ng_html_snapshot to the data object passed into grunt.initConfig().
grunt.initConfig({
ng_html_snapshot: {
options: {
// Task-specific options go here.
}
}
});Type: String
Base url of your application / website in form of: protocol://host. Make sure that your web server is up and running if you running web application locally. For example, http://localhost:8080
Type: String
Default: './node_modules/grunt-ng-html-snapshot/utils/phantom-job.js'
Path to a phantom.js job (relatively to Gruntfile.js) which contains logic for building web pages snapshots. Change it only if you need custom phantom.js logic and you know what you are doing.
Type: Object
An object with output details
Type: String
Output directory relative to Gruntfile.js
Type: String
Snapshot file extension. If you would like to output each page snapshot without file extension, then either pass false or omit this param.
Type: String
Path to log file with a results of phantom.js actions. If you don't need such a log, then either pass false or omit this param.
Type: Number
Default: 100
If page wasn't successfully loaded during first attempt, then timeout is used as an interval before executing next attempt.
Type: Boolean
Default: true
Set this flag to false if you don't need to remove from a page snapshot. This might be necessary for some search engines. For example, this tag should be removed from a page so that it can be indexed by Yandex bot. [See details here] (https://yandex.com/support/webmaster/robot-workings/ajax-indexing.xml)
Type: String
Default: '<!doctype html>'
Document type (for example, '<!doctype html>', '', etc).
Type: Array
Array of target pages. Each object in this array has to have two fields: path and file. 'path' is added to baseUrl (options.output.baseUrl) in order to construct page's absolute url. 'file' is added to output directory path (options.output.dir) and result is merged with file extension (only if it was set) in order to get an absolute path to a file with page snapshot.
grunt.initConfig({
ng_html_snapshot: {
options: {
/*
* Keep in mind, that you have to have a running web server, if you running
* your web application locally.
*/
baseUrl: 'http://localhost:8080',
/*
* Overriding default path to phantom.js job.
* Note: path is relative to Gruntfile.js
*/
jobPath: './some-folder/some-custom-phantom-job.js',
output: {
// Output directory. In case if doesn't exists phantom creates it.
dir: './html-snapshots',
snapshotFileExt: 'html',
// If you don't want to log job actions, then use false as a value.
logFile: 'job-log.txt'
},
pageLoadingTimeout: 100,
pageDocType: '<!doctype html>',
/*
* Overriding default parameter, hence
* <meta name="fragment" content="!" />
* will not be removed from snapshot (s) if
* it was presented in the original page (s).
*/
removeMetaFragment: false,
pages: [
{
path: '/path-to-page-a',
file: 'page-a'
},
{
path: '/',
file: 'main-page'
},
{
path: '/path-to-page-b',
file: 'page-b'
}
]
}
}
});In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality.
0.1.4 - bug fixes. 0.1.3 - Fix for gathering documentHtml in the default phantom.js job 0.1.2 - bug fixes. Improved method for checking page loading status. 0.1.0 - first version. No threshold for checks for page loading status. The process will be killed by timeout after 5 minutes.