You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2020. It is now read-only.
Recent versions of Jasmine have support for node.js, in that they export to exports instead of window. So you should be able to drop the window hacks before and after loading jasmine and instead say:
var jasmine = require('jasmine.js'); // you have to say jasmine.jasmine for the "main" jasmine object
It would probably take a little re-architecturing seeing as jessie/jasmine.js doesn't export the jasmine object (I guess it ends up getting put in global), but beyond that I don't see any problems... jessie seems like it's not too complicated.
Anyway at the moment this doesn't bother me, but when it does I can probably take a look at this.
The text was updated successfully, but these errors were encountered:
Recent versions of Jasmine have support for node.js, in that they export to
exports
instead ofwindow
. So you should be able to drop thewindow
hacks before and after loading jasmine and instead say:It would probably take a little re-architecturing seeing as jessie/jasmine.js doesn't export the
jasmine
object (I guess it ends up getting put inglobal
), but beyond that I don't see any problems... jessie seems like it's not too complicated.Anyway at the moment this doesn't bother me, but when it does I can probably take a look at this.
The text was updated successfully, but these errors were encountered: