From ef6e195e89a323e59464eeedaca02727ba75e7d6 Mon Sep 17 00:00:00 2001
From: felipe <felipe@fov.space>
Date: Wed, 8 Mar 2017 14:15:48 +0100
Subject: [PATCH] add an .npmignore file which does not exclude the build dir

Per https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package,
npm automatically uses .gitignore if there is no .npmignore, which may
have been keeping the build dir out of the package
---
 .npmignore | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 .npmignore

diff --git a/.npmignore b/.npmignore
new file mode 100644
index 0000000000..672b7f7700
--- /dev/null
+++ b/.npmignore
@@ -0,0 +1,40 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directory
+node_modules
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# build
+# build  <-- we want this in the package
+build-tests
+
+# vscode
+.vscode