Use node to run eslc binary

bin/eslc.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+// Simple wrapper script for src/cli.ls, independent of the build system.
+require("../lib/cli")

doc/basics-reference.markdown

@@ -66,7 +66,7 @@ those later.)
 
 ## Compilation
 
-<!-- !test program ./bin/eslc | head -c -1 -->
+<!-- !test program node ./bin/eslc.js | head -c -1 -->
 
 When you hand your code to the eslisp compiler, it reads the lists and turns
 them into JavaScript code with the following rules:

doc/how-macros-work.markdown

@@ -5,7 +5,7 @@ differently, but call them the same way as normal functions.  They can execute
 whatever logic you want, and their return values become program code at the
 point where they're called.
 
-<!-- !test program ./bin/eslc | head -c -1 -->
+<!-- !test program node ./bin/eslc.js | head -c -1 -->
 
 ## The basics
 

package.json

@@ -15,7 +15,7 @@
     "doc": "./doc"
   },
   "bin": {
-    "eslc": "./bin/eslc"
+    "eslc": "./bin/eslc.js"
   },
   "files": [
     "lib",

readme.markdown

@@ -11,7 +11,7 @@ your own language features, [like this][9].
 > :warning: **Note the 0.x.x [semver][10].**  The API may shift under your
 > feet.
 
-<!-- !test program ./bin/eslc | head -c -1 -->
+<!-- !test program node ./bin/eslc.js | head -c -1 -->
 
 <!-- !test in fib -->
 

test.ls

@@ -872,9 +872,9 @@ test "macros can be required relative to root directory" ->
     (x)
     """
 
-  eslc-path = path.join process.cwd!, "bin/eslc"
+  eslc-path = path.join __dirname, "bin/eslc.js"
   try
-    exec-sync "#eslc-path #main-basename", cwd : dir-name
+    exec-sync "node #eslc-path #main-basename", cwd : dir-name
       ..to-string! `@equals` "\n"
   finally
     e <~ rimraf dir-name