@nathf/puppeteer-healthcheck - npm Package Compare versions

Comparing version 0.0.1 to 0.1.1

package.json

 {
   "name": "@nathf/puppeteer-healthcheck",
-  "version": "0.0.1",
+  "version": "0.1.1",
   "description": "",
@@ -25,3 +25,2 @@ "main": "lib/puppeteer-healthcheck.js",
     "ansi-colors": "^1.1.0",
-    "fancy-log": "^1.3.2",
     "puppeteer": "^1.1.1",
@@ -28,0 +27,0 @@ "yargs": "^11.0.0"

README.md

@@ -0,6 +1,8 @@
+[![NPM](https://img.shields.io/npm/v/@nathf/puppeteer-healthcheck.svg)](https://www.npmjs.com/package/@nathf/puppeteer-healthcheck)
+![CircleCI branch](https://img.shields.io/circleci/project/github/nathf/puppeteer-healthcheck/master.svg)
+![Docker Build Status](https://img.shields.io/docker/build/nathf/puppeteer-healthcheck.svg)
+
 # Puppeteer Healthcheck
 Puppeteer Healthcheck is a simple tool wrapped over [puppeteer](https://github.com/GoogleChrome/puppeteer) to check page and critical asset status', as well as checks for key dom elements.
 
-[![nodesource/node](http://dockeri.co/image/nathf/puppeteer-healthcheck)](https://hub.docker.com/r/nathf/puppeteer-healthcheck/)
-
 ## The Problem
@@ -7,0 +9,0 @@ Often post deploy we want to check our site/app has been deployed sucessfully. We would want to ensure the web server is responding, critical assets and certain DOM elements exists post deploy.

No alert changes

Improved metrics

Total package byte prevSize

9305

increased by1.91%

Dependency count

3

decreased by-25%

Number of lines in readme file

68

increased by3.03%

Dependency changes

• - Removedfancy-log@^1.3.2

• - Removedansi-gray@0.1.1(transitive)

• - Removedcolor-support@1.1.3(transitive)

• - Removedfancy-log@1.3.3(transitive)

• - Removedparse-node-version@1.0.1(transitive)

• - Removedtime-stamp@1.1.0(transitive)