From 7f5f4d60b70909d21e0111d2c900ba0f5993b374 Mon Sep 17 00:00:00 2001 From: Mihai Bazon Date: Mon, 5 Nov 2012 22:23:51 +0200 Subject: [PATCH] discard the hack that worked around the deprecation warning (since the source-map module no longer uses require.js) refs #9 --- tools/node.js | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/tools/node.js b/tools/node.js index 4a891380..be3cd93d 100644 --- a/tools/node.js +++ b/tools/node.js @@ -1,18 +1,5 @@ var path = require("path"); var fs = require("fs"); - -// Avoid NodeJS warning. -// -// There's a --no-deprecation command line argument supported by -// NodeJS, but that's tricky to use, so I'd like to set it from the -// program itself. Turns out you need to set `process.noDeprecation`, -// but by the time you can set that the `path` module is already -// loaded and `path.existsSync` is already changed to display that -// warning, therefore here's the poor solution: -if (fs.existsSync) { - path.existsSync = fs.existsSync; -} - var vm = require("vm"); var sys = require("util");