Node Wraith

A responsive screenshot comparison tool. Based on the Ruby version available at (
Alternatives To Node Wraith
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
5 months agomitVue
Responsive ecommerce template built with Vue.js and Nuxt.js
Break Shot176
7 years ago6mitCSS
Desktop app for capturing screenshots of responsive websites
5 years ago4mitHTML
UIAdmin - UI Kit 3 Responsive Admin Panel
Node Wraith34247 years ago21January 04, 20154JavaScript
A responsive screenshot comparison tool. Based on the Ruby version available at (
Capybara Paparazzi22
4 years agomitRuby
Ruby gem for taking responsive screenshots
5 years ago2JavaScript
Adaptation of ModularAdmin for Osticket v.1.11
7 years agoSeptember 21, 20164CSS
A small CSS library for adding responsive frames (mobile device, desktop computer, or browser toolbar) to images
7 years ago3gpl-2.0JavaScript
Flusk - A Responsive Multi-purpose Website Template with bootstrap 3
Responsive Screenshots14
11 years agoJavaScript
CasperJS script for taking screenshots on responsive screensizes
Adminlte Angular214
7 years agootherHTML
Alternatives To Node Wraith
Select To Compare

Alternative Project Comparisons


A responsive screenshot comparison tool. It can be used for regression testing or cross browser testing

Based on the Ruby version available at BBC-News/wraith

CLI app


	npm install -g wraith


wraith --config <config>

-h, --help				Output help information
-v, --version			Output version information
-c, --config [config]	Specify the location of the configuration file
-q, --quiet				All logging is hidden

wraith --config ./config/chrome

Configuration file

Wraith uses a json based configuration file that allows you specify a large number of options. You can create as many configurations files as you need and call them from the cli using the --config flag.

Below is an example configuration file:

	Optional name for the project, if supplied it will be used within the generated
	gallery only
	"project": "Test",

	Specify one or two domains
	"domains": [

	Engines supported are phantomjs and slimerjs but in theory any phantomjs based
	headless browser can be supported.

	To do cross browser testing specify one domain and two engines or your choice
	"engines": [

	Specify as many sizes as you wish. If no sizes are specified then the most
	popular sizes will be used based on the information provided by stats
	"sizes": [

	Output directory within the /shots directory
	"outputDir": "test/chrome/",

	You can specify a list of paths to be used or you can crawl the site.
	Note: If paths are provided they will take precedent and the spider file
	will be ignored.

	"paths": [

	If no paths are specified then a site crawl will take place and the results
	will be save in the location specified within this option
	"spider": "spider/test.txt",

	Limit the amount of concurrent processes
	"maxConnections": 20

###API This is very basic at the minute but you can use wraith within your applications.

At the minute there is only one option which is to run the application with a given config file and then run a specified callback but I am looking to expand this in the future.

npm install wraith --save-dev

var wraith = require('wraith');
var config = require('./config/chrome');

new Wraith(config, function() {
	console.log('Callback, do something else here!');

As the config is just an object you can change it at any point before calling
the wraith function e.g.

config.maxConnections = 10;
config.quiet = true;

new Wraith(config, function() {
	console.log('Callback, do something else here!');


MIT James Bell

Popular Screenshot Projects
Popular Responsive Projects
Popular Media Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Command Line App
Cross Browser