There is a bug with formage that is plaguing us right now.

Once node4good/formage#122 is fixed, we will switch to whatever the next
release is.

package.json

@@ -14,7 +14,7 @@
     "errorhandler": "^1.4.1",
     "express": "^4.14.1",
     "express-session": "^1.15.1",
-    "formage": "~3.3.0",
+    "formage": "git+http://github.com/robbyoconnor/formage#fix-issue-122",
     "ldapjs": "^1.0.0",
     "less-middleware": "~2.2.0",
     "lodash": "^4.17.4",

yarn.lock

@@ -867,9 +867,9 @@ [email protected]:
   dependencies:
     lodash "~2.0.0"
 
-formage@~3.3.0:
+"formage@git+http://github.com/robbyoconnor/formage#fix-issue-122":
   version "3.3.0"
-  resolved "https://registry.yarnpkg.com/formage/-/formage-3.3.0.tgz#77ff6e4f12542a8586a089274153366192128f05"
+  resolved "git+http://github.com/robbyoconnor/formage#dbbfa519a0d305bf01d6116b653e505ed8390029"
   dependencies:
     async "^0.9.0"
     basic-auth "^1.0.0"