Awesome, that did it. Thanks!
On Tue, Jun 25, 2013 at 1:34 PM, Jarrod Overson <[email protected]> wrote: > It looks like line 89 in test/runner.js was expecting a callback and line > 123 in Gruntfile.js wasn't passing one, changing > > Gruntfile.js:123 require('./test/runner').node(); > > to > > Gruntfile.js:123 require('./test/runner').node(done); > > allows the tests to run (on my machine). > > I'm not in a place to do a PR, but hope this helps. > > In the future, running grunt with -v and --stack will give you more to go > on. > > -- > Jarrod Overson > tw <https://twitter.com/jsoverson> | gh <http://github.com/jsoverson> > | g+<http://profiles.google.com/jsoverson> > | li <http://jarrodoverson.com/linkedin> > > > > > On Tue, Jun 25, 2013 at 1:22 PM, Joe Bowser <[email protected]> wrote: > >> Cool, can you download the repo and run grunt and see if you can reproduce >> this? >> >> On Tue, Jun 25, 2013 at 1:20 PM, Jarrod Overson <[email protected]> >> wrote: >> > Joe, let me know if I can help out with grunt at all. I'm a member of the >> > grunt team and think it would be perfect for cordova. >> > >> > -- >> > Jarrod Overson >> > tw <https://twitter.com/jsoverson> | gh <http://github.com/jsoverson> >> > | g+<http://profiles.google.com/jsoverson> >> > | li <http://jarrodoverson.com/linkedin> >> > >> > >> > On Tue, Jun 25, 2013 at 1:17 PM, Joe Bowser <[email protected]> wrote: >> > >> >> Hey >> >> >> >> I gave up on coho, so just to do sanity, I tried using grunt to >> >> generate the packages, and I get the following after the unit tests >> >> finish. >> >> >> >> Fatal error: undefined is not a function >> >> >> >> So, what runs after the tests again? Should we just not care about >> >> this? I'm not familiar with grunt enough to know why I would get this >> >> once the tests are done. I seem to have the JS, so I'm OK to roll >> >> with it, but I would like to know why. >> >> >> >> Joe >> >> >>
