- fix babel issues reported in tj#12 (and still not fixed in tj#16): when babel has transpiled all assert(...) calls to something else ((0, _.default)(...) for example), we look for that transpiled code instead. (assuming Babel 7)

  Defensive coding ensures no crash when these assumptions don't match reality: instead of the function arguments, '???' is reported instead.
- Completely removed obsolete callsite references in the code.

Author: GerHobbelt

index.js

@@ -3,7 +3,6 @@
  */
 
 var AssertionError = require('assert').AssertionError
-  , callsite = require('callsite')
   , fs = require('fs');
 
 /**
@@ -34,7 +33,14 @@ function assert(expr) {
     var lineno = parseInt(m[3]);
     var fullsource = fs.readFileSync(file, 'utf8');
     var line = fullsource.split('\n')[lineno-1];
-    var src = line.match(/.*assert\((.*)\)/)[1];
+    var m = line.match(/assert\((.*)\)/);
+    if (!m) {
+        // however, if the entire file doesn't carry any assert() lines any more,
+        // our next bet is this source file was transpiled by babel:
+        m = line.match(/\(0, [\w_]+\.default\)\((.*)\)/);
+    }
+
+    var src = m ? m[1] : "???";
     var err = new AssertionError({
         message: src + "\n ",
         stackStartFunction: assert

package.json

@@ -14,9 +14,7 @@
         "TonyHe <[email protected]>",
         "ForbesLindesay"
     ],
-    "dependencies": {
-        "callsite": "1.0.0"
-    },
+    "dependencies": {},
     "repository": {
         "type": "git",
         "url": "https://github.com/visionmedia/better-assert.git"