Originally a follow-up to issue #223 by @ramses0.
$ mojito version
path.existsSync is now called fs.existsSync.
Version of mojito is 0.3.30
$ mojito test app .path.existsSync is now called fs.existsSync.
[warn] undefined: overriding application config value: env
[WARN] MojitoServer: your mojit "HelloMojit" has a server affinity and these client-related deps: node-base, node-core, dom-core, dom-base, node-event, node-pluginhost, node-screen, dom-screen, dom-style, dom-style, node-style
[WARN] MojitoServer: Mojito may be unable to start, unless you have provided server-side DOM/host-object suppport
if (!process.listeners('uncaughtException').length) throw e;
TypeError: Cannot read property 'documentElement' of null
at Object.YUI.add.requires as fn
...tutorial or mojito is broken.
Yep, this is "base case" stupidly following the tutorial. I tried changing controller.server.js to controller.client.js to maybe adjust the "affinity" (?) but it gave different error messages which I am not familiar enough with mojito / node to figure out off the top of my head.
Quickstart worked: http://developer.yahoo.com/cocktails/mojito/docs/quickstart/ but the "HelloWorld" has not. Literally just mojito create app ; mojito create mojit ; mojito start as suggested by the tutorial.
This is with latest npm / node and the 0.3.30 mojito freshly downloaded. npm install mojito -g ... and copy/paste all the config stuff from the tutorial examples. Server starts after tweaking, but gives a different error message which I don't have on this computer. Shouldn't be hard to reproduce.
I've added this to the sprint for investigation.
@jenny I was approached by several people in Bangalore about this. The breaking/crashing unit tests are fixed with: #395
still no fix? I just started playing with Mojito, and breaking a HelloWorld app makes it look pretty bad...
@bitlyfied it was fixed in 0.4.2 few days ago, but it is not tagged as stable yet!
Fixed in 0.4.2. Closing.