Getting started app not working (under node 0.10.22)

[Chris Toomey]

Hi,

Just came across this today after seeing Patrick's NodeSummit tweet and after following the Getting Started instructions am getting a node server error when hitting http://localhost:8080/.  The stack trace is below.

I'm running node v0.10.22.  It doesn't sound like a node version issue but is it, and what version of node should it work on?  Or maybe something's missing from the config. for the generated app?

thx,

Chris

ERROR express-raptor/RequestContext:

Error: Call to context.renderTemplate("/ui/pages/index/index.rhtml", ...) failed: ReferenceError: window is not defined

    at onError (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/express-raptor/RequestContext.js:101:55)

    at _rejected (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:808:24)

    at /home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:834:30

    at Promise.when (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:1079:31)

    at Promise.promise.promiseDispatch (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:752:41)

    at /home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:526:49

    at flush (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/node_modules/q/q.js:108:17)

    at process._tickCallback (node.js:415:13)

Caused by:

ReferenceError: window is not defined

    at Object.<anonymous> (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/rebootstrap/node_modules/bootstrap/js/bootstrap-button.js:105:3)

    at Module._compile (module.js:456:26)

    at Object.Module._extensions..js (module.js:474:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

    at Module.require (module.js:364:17)

    at require (module.js:380:17)

    at Object.require (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/lib/raptor/runtime/runtime_node.js:26:13)

    at Object.evaluateResource (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/lib/raptor/runtime/runtime.js:34:26)

    at Dependency.load (/home/ctoomey/devct/nodejs/raptor/demo/node_modules/raptor/lib/raptor/packaging/Dependency.js:138:25)

[Patrick Steele-Idem]

Hi Chris,

Thanks for trying out RaptorJS and discovering the bug! It looks like some recent changes broke the rebootstrap module. I ended up having to revert a recent commit. Please try again after running the following command to get the fix:

npm install raptor@~2.5.12 --save

Please let us know if you run into any other issues.

Thanks,

Patrick

[Chris Toomey]

It's not finding the tarball for that version:

% npm install raptor@~2.5.12 --save

npm http GET https://registry.npmjs.org/raptor

npm http 200 https://registry.npmjs.org/raptor

npm http GET https://registry.npmjs.org/raptor/-/raptor-2.5.12.tgz

npm http 404 https://registry.npmjs.org/raptor/-/raptor-2.5.12.tgz

npm ERR! fetch failed https://registry.npmjs.org/raptor/-/raptor-2.5.12.tgz

--
You received this message because you are subscribed to a topic in the Google Groups "RaptorJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/raptorjs/5CBrccjn5PM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to raptorjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Patrick Steele-Idem]

Hi Chris,

It is really unfortunate, but the public npm registry has been in really bad shape lately. For some reason it lost the attachment with the previously published version (even though the metadata for the new version still existed in the registry). It was working yesterday...

I was not able to publish over the invalid module because of additional problems with the public npm registry so I had to up the version to 2.5.13. Please try the following:

npm install raptor@~2.5.13 --save

Hopefully that works for you. It is working for me...at least for now.

Thanks again,

Patrick

[Chris Toomey]

Ok, that fixed it, thanks.  I've got some other questions but will ask those in a new thread.

Chris