From 6a6ed5a21485758bd754baaa3ce4618cce21fb84 Mon Sep 17 00:00:00 2001
From: Yavor Georgiev <fealebenpae@gmail.com>
Date: Thu, 21 Jul 2016 17:39:03 +0200
Subject: [PATCH] Get the path to nan relatively

Under npm3 the `realm` and `nan` modules might end up as siblings so the best way to get the path to `nan` is to require it from within the `realm` module. The `nan` module prints its path so it can be captured by an external build system like in this patch.
---
 src/node/binding.gyp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/node/binding.gyp b/src/node/binding.gyp
index 2f273d28..b9305c5b 100644
--- a/src/node/binding.gyp
+++ b/src/node/binding.gyp
@@ -34,7 +34,7 @@
         "../object-store/src/parser",
         "../object-store/external/pegtl",
         "../../core-node/include",
-        "../../node_modules/nan"
+        "<!(node -e 'require(\"nan\")')"
       ],
       "library_dirs": [
         "$(srcdir)/../../core-node"