No stack on assertion error in PhantomJS

Steps to reproduce:

1. Install PhantomJS

   npm install -g phantomjs-prebuilt
   

2. Download the chai browser build into a dir, save it as chai.js.

3. Create test.html in the same dir with these contents:

   <script src="chai.js"></script>
   <script>
   try {
     chai.expect(1).to.equal(2);
   }
   catch (error) {
     console.log('Stack on chai assertion error:', error.stack);
   }
   
   try {
     throw new Error('regular');
   }
   catch (error) {
     console.log('Stack on regular error:', error.stack);
   }
   
   window.close();
   </script>
   

4. Create test.js in the same dir with these contents:

   var page = require('webpage').create();
   page.onConsoleMessage = console.log.bind(console);
   page.onClosing = phantom.exit;
   page.open('test.html');
   

5. Execute on the command line in that dir:

   phantomjs test.js
   

Expected result:

• Both the assertion error and the regular error have stack information.

Actual result:

• The regular error has stack information, but the assertion error’s stack is undefined.

In Chrome, however, both errors have a proper stack.

Tested with chai 3.5.0 and PhantomJS 2.1.1

[keithamus]

Soon @eekboom, soon.

[meeber]

@xcafebabe Yup you’re right, I forgot that we don’t currently regenerate the chai.js file on every commit to the master branch. On the plus side, we’ll be releasing an alpha release of Chai 4.0 very soon that will have this change. And going forward we plan on releasing new versions more rapidly using semantic release.

An interim solution is to clone the chai repo and run npm install && npm test and it will regenerate chai.js with the patch included.