From babea5e02c2c74b78b1c47618e93434cf8af5b0a Mon Sep 17 00:00:00 2001
From: Jason Miller <developit@users.noreply.github.com>
Date: Tue, 15 Mar 2016 13:40:32 -0400
Subject: [PATCH] Fix options not being passed to npm-http-server

`npm-http-server` expects options as a hash, but they were being passed as arguments. This did not affect npmcdn.com because the defaults were being used anyway, but I ran into it when setting it up internally at my company. #TrolledByMJ again
---
 server.js | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/server.js b/server.js
index 3397f07..ec06766 100644
--- a/server.js
+++ b/server.js
@@ -10,10 +10,10 @@ const app = express()
 app.disable('x-powered-by')
 app.use(cors())
 app.use(express.static('public', { maxAge: 60000 }))
-app.use(createRequestHandler(
-  registryURL,
-  bowerBundle
-))
+app.use(createRequestHandler({
+  registryURL: registryURL,
+  bowerBundle: bowerBundle
+}))
 
 app.listen(port, function () {
   console.log('Server started on port %s, Ctrl+C to quit', port)