Document changes, ignore more files, release 0.1.13

.npmignore

@@ -2,3 +2,4 @@
 node_modules
 src
 __test__
+example/

.travis.yml

@@ -1,4 +0,0 @@
-language: node_js
-node_js:
-- "8"
-- "10"

README.md

@@ -1,4 +1,11 @@
 ## Go NPM
+
+### (@gzuidhof): MODIFICATIONS FROM BASE `go-npm` PACKAGE
+* Support for zip and non-compressed binaries.
+* Added support for `arm64` architecture.
+* Fix for use on Windows platform (the binary would get placed in the wrong place for consumers).
+* Shipped as a bundle using `esbuild`, removing 70 packages of dependencies (including huge things like Babel). Now your users will only have to download one additional package (`@guidhof/go-npm`).
+
 ### Distribute cross-platform Go binaries via NPM
 
 Applications written in Golang are portable - you can easily cross-compile binaries that work on Windows, Mac, and Linux. But how do you distribute the binaries to customers? When you publish new releases, how do they update the binary?

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@gzuidhof/go-npm",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "lockfileVersion": 2,
   "requires": true,
   "packages": {
     "": {
       "name": "@gzuidhof/go-npm",
-      "version": "0.1.12",
+      "version": "0.1.13",
       "license": "Apache-2.0",
       "bin": {
         "go-npm": "bin/index.js"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gzuidhof/go-npm",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "Distribute and install Go binaries via NPM",
   "main": "index.js",
   "bin": {