Chris M
Chris M
Why not use an `afterEach` in your describe block?
Well, first thing off the top of my head (not ideal) is you can use the force exit flag when you run jasmine node. I'll think about other solutions today....
Lemme know how that goes.
In v0.8.21 I get: ``` cmoultrie@Sauron~/G/jasmine-node (master) $ jasmine-node spec/SampleSpecs.jsa fs.js:524 return binding.stat(pathModule._makeLong(path)); ^ Error: ENOENT, no such file or directory '/Users/cmoultrie/Git/jasmine-node/spec/SampleSpecs.jsa' at Object.fs.statSync (fs.js:524:18) at Object.jasmine.loadHelpersInFolder (/usr/local/lib/node_modules/jasmine-node/lib/jasmine-node/index.js:42:20) at Object....
What version of node and coffee-script are you running? I saw in 0.10.0 that imports just started failing silently instead of crashing. On Apr 6, 2013, at 11:12 AM, "Jarek...
Okay. Can you open up the node repl and type: `require('fakename')` and see if the repl exceptions? I'm not near a box I can try that on. If it does...
Okay, I'll promote this to a real issue and try to figure out what is going on. It may be that as the vm gets built up it supresses that...
@chenglou @pako1337 Can you guys test the [beta1.5.1](https://github.com/mhevery/jasmine-node/tree/beta1.5.1) branch? This fixes it in all my tests, but I'd like a second set of eyes.
As in, exceptions while passing the file to coffee-script for compilation? And yes, that was the output I was expecting.
Okay, I'll look into that, hopefully it'll be pretty much the same.