From 018e6bec1775d4a6442e2554e510a989c8f0d3be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=A1=D0=BA=D0=BE=D0=B2=D0=BE=D1=80=D0=BE=D0=B4=D0=B0=20?=
 =?UTF-8?q?=D0=9D=D0=B8=D0=BA=D0=B8=D1=82=D0=B0=20=D0=90=D0=BD=D0=B4=D1=80?=
 =?UTF-8?q?=D0=B5=D0=B5=D0=B2=D0=B8=D1=87?= <chalkerx@gmail.com>
Date: Sat, 3 Mar 2018 01:17:09 +0300
Subject: [PATCH] fix(middleware): avoid using deprecated Buffer API

safe-buffer is already used and provides Buffer.alloc polyfill, so
just use Buffer.alloc directly to avoid hitting deprecated API.

Refs:
https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor
---
 lib/middleware/common.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/middleware/common.js b/lib/middleware/common.js
index 96ac2df29..2eea405d8 100644
--- a/lib/middleware/common.js
+++ b/lib/middleware/common.js
@@ -58,7 +58,7 @@ var createServeFile = function (fs, directory, config) {
           return 206
         } else {
           // Multiple ranges are not supported. Maybe future?
-          responseData = new Buffer(0)
+          responseData = Buffer.alloc(0)
           return 416
         }
       }